x402-data-gateway

Extract Public URLs in Batch

extract_batch

Fetch one to five public HTTPS URLs and return bounded structured fields for each source in one paid attempt. Supply urls as a JSON array and optional unique fields. Use extract for a single URL when you do not need batch accounting. Charge is one flat introductory 0.01 USDC quote for the bounded attempt, not a guarantee that every URL succeeds. Automatic retries are disabled; unknown outcomes must not be re-paid automatically. Payment challenge and credentials are bound to POST https://agents.samedaydesk.com/extract/batch, not mcp://. Retry the identical authorized arguments and credential.

Input Schema

Name	Required	Description
`urls`	Yes	One to five public HTTPS URLs as a JSON array. Charge is one flat introductory attempt, not per-URL success.
`fields`	No	Optional unique bounded subset of structured extraction fields.
`textExcerptLimitChars`	No	Optional per-item excerpt budget. Omitted requests keep 1200. A value that cannot fit the batch response ceiling is rejected before fetch. Does not change the price.

Output Schema

Name	Required	Description	Default
`ok`	Yes
`error`	No
`jobId`	Yes
`quote`	Yes
`charged`	Yes
`partial`	Yes
`product`	Yes
`sources`	Yes
`boundary`	Yes
`jobStatus`	Yes
`accounting`	Yes
`costInputs`	Yes
`stopReason`	Yes
`schemaVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 4, 2026

addedInput schema / properties / textExcerptLimitChars

Added value: +{
+  "description": "Optional per-item excerpt budget. Omitted requests keep 1200. A value that cannot fit the batch response ceiling is rejected before fetch. Does not change the price.",
+  "maximum": 40000,
+  "minimum": 1,
+  "type": "integer"
+}

AddedSep 8, 2026

TDQS

A4.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does so: it discloses a flat 0.01 USDC introductory charge that is not a per-URL success guarantee, disables automatic retries, warns against re-paying unknown outcomes, and specifies that the payment challenge is bound to the HTTPS POST endpoint rather than mcp://. This is exactly the behavioral context an agent needs for a paid, non-idempotent call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with purpose and scoping, and most sentences earn their place by covering cost, retry, and credential binding. There is mild redundancy, since the flat charge is stated in both the description and the `urls` schema, keeping it just short of a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values need not be explained, and the description still supplies the payment, retry, and endpoint-binding context that annotations would otherwise provide. Nothing an agent needs to invoke this paid batch tool correctly appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents `urls`, `fields`, and the excerpt budget. The description restates `urls` and `fields` semantics but never mentions `textExcerptLimitChars`, adding little beyond structured data. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence states a concrete verb+resource+scope ('Fetch one to five public HTTPS URLs and return bounded structured fields for each source in one paid attempt'). It also explicitly distinguishes itself from the sibling `extract` for single-URL use, so an agent can route between them without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names the alternative ('Use `extract` for a single URL when you do not need batch accounting') with the selecting condition, and gives explicit retry guidance ('Retry the identical authorized arguments and credential') plus a when-not ('unknown outcomes must not be re-paid automatically').

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All x402-data-gateway tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.