Web Page Metadata API.
Extract SEO, Open Graph, Twitter and technical metadata from public web pages for automated analysis and AI agent workflows.
Website metadata
without manual browsing.
Analyze the metadata layer of a public URL using a compact, machine-readable API response.
GET /v1/web/metadata
Pass a public page URL using the url query parameter.
SEO + social metadata
Extract page signals used for search and social sharing analysis.
Website intelligence
Useful for SEO auditing, content research, competitive analysis and automated website profiling.
Designed for machines.
Use OpenAPI and DataBG discovery to connect metadata extraction to autonomous workflows.
View OpenAPI →API reference for AI agents and developers.
DataBG tools are designed as small, machine-readable building blocks for automated workflows. Each request uses a predictable HTTP endpoint and can be accessed with an API key or, where enabled, through x402 machine payments.
Extract SEO and social metadata programmatically
The DataBG Web Page Metadata API is built for applications and AI agents that need to inspect the metadata layer of a public web page. It extracts SEO, Open Graph, Twitter and technical metadata as structured JSON, making website analysis easier to automate.
Request
GET https://api.databg.tech/v1/web/metadata?url=https://example.comRequired parameter: url — the public HTTP or HTTPS page to inspect.
Metadata signals
The tool is intended to expose the page-level signals used for search presentation, social sharing and technical website analysis. This makes it useful for SEO auditing, content research, competitive analysis, automated website profiling and agent-based research.
Why agents use metadata
An autonomous agent can use page metadata as a fast first layer of website understanding before requesting full page extraction. For example, an agent can inspect a title, description or social preview signal and then decide whether deeper extraction is necessary.
Access and errors
The current production service requires a DataBG API key or an x402 payment. The listed price is $0.003 per request in USDC on Base Mainnet. Clients should handle invalid URL requests, HTTP 402 payment requirements and upstream fetch or parsing errors.
SEO use cases
Common applications include programmatic SEO checks, website inventories, content research, metadata quality analysis, competitor discovery and automated enrichment. The API returns data for software consumption rather than requiring an interactive browser.
How x402 access works
DataBG paid tools can use the HTTP 402 Payment Required flow. A compatible client requests a resource, receives machine-readable payment requirements, settles the requested amount in USDC on Base Mainnet, and retries the request with payment authorization. This model is designed for autonomous software that can discover and pay for individual API calls.
Agent → DataBG endpoint
↓
402 Payment Required
↓
USDC payment on Base Mainnet
↓
Retry with payment authorization
↓
Structured JSONFor implementation details, use the live API specification and machine-readable discovery resources linked below.
Open API specification → Machine-readable discovery →