API Docs↗
WEB INTELLIGENCE

Web Page Extraction API.

Fetch a public web page and turn its accessible content into structured data for AI agents and automated applications.

$0.005Per request
USDCPayment currency
BaseMainnet
x402Machine payment
WEB EXTRACTION

Public web content
as structured JSON.

Give an agent a public URL and receive structured metadata, visible text and links through a single API request.

ENDPOINT

GET /v1/web/extract

Pass a public page URL using the url query parameter.

?url=https://example.com
OUTPUT

Extracted page data

Designed to make public web content easier for software to consume and combine with other tools.

TextMetadataLinksJSON
USE CASES

Agent research

Useful for research agents, website analysis, content pipelines and automated web intelligence.

ResearchExtractionAgents
API DISCOVERY

Fetch. Parse. Continue.

Integrate the extraction endpoint through the DataBG OpenAPI specification and machine-readable discovery.

View OpenAPI →
DETAILED DOCUMENTATION

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.

WEB PAGE EXTRACTION API

Extract public web pages into structured data

The DataBG Web Page Extraction API lets an AI agent, developer application or automated workflow fetch a public HTTP or HTTPS page and receive structured metadata, visible text and links. It is useful when an agent needs to read public web content without implementing its own page-fetching and parsing layer.

Request

GET https://api.databg.tech/v1/web/extract?url=https://example.com

Required parameter: url — a public HTTP or HTTPS URL to extract. The live API specification defines the parameter as a URI.

What the response is designed for

The response is machine-readable JSON containing extracted page information. The tool is particularly useful for AI research agents, content pipelines, website intelligence, document enrichment, monitoring workflows and applications that need to combine web content with other structured signals.

Typical agent workflow

An agent can identify a URL, call the extraction endpoint, inspect the returned text and links, and then pass the structured result to another reasoning or analysis step. This avoids coupling the agent to a browser-specific scraping implementation.

Errors and access

Clients should handle invalid or missing URLs, payment requirements and upstream fetch or parsing failures. Paid access can return HTTP 402 Payment Required before the successful JSON response. The current production endpoint is priced at $0.005 per request in USDC on Base Mainnet.

Best practices

  • Send canonical public URLs whenever possible.
  • Validate that the target is intended to be publicly accessible.
  • Handle HTTP 400, 402, 500 and 502 responses in automated workflows.
  • Use the Web Page Metadata API when only metadata is required.
MACHINE PAYMENTS

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 JSON

For implementation details, use the live API specification and machine-readable discovery resources linked below.

Open API specification → Machine-readable discovery →