DropEngine x402 Agent Services

extract_structured

Paid Fresh Structured Extract ($0.01 USDC). Extracts a fresh webpage into a simple agent-defined typed JSON shape, with validation and per-field provenance. Uses static page data only; never executes page JavaScript and never fabricates missing fields.

Agent entry points: risky external action → use Agent Action Gate when a combined action-specific safety assessment is needed; unclear capability/provider → use free /api/discover; constrained comparison between callable alternatives → use paid route_tool; known single capability → call the direct tool; multi-step objective → read the matching workflow recipe and call only relevant steps. Workflows are stateless recipes, not executors; calls are paid separately and are not bundle charged. Agent Action Gate does not approve payment, sign or broadcast transactions, evaluate seller reputation, replace transaction simulation, replace route_tool, or replace human approval.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`schema`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`data`	Yes
`meta`	No
`next`	No
`error`	No
`cached`	Yes
`result`	No
`status`	No
`payment`	No
`success`	Yes
`agent_ux`	No
`final_url`	Yes
`confidence`	Yes
`provenance`	Yes
`validation`	Yes
`extracted_at`	Yes
`data_age_seconds`	Yes
`recommended_next`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 8, 2026

addedOutput schema / properties / recommended_next / properties / recommendation_id

Added value: +{
+  "format": "uuid",
+  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+  "type": "string"
+}

Changed11 schema fields changedOct 8, 2026

addedOutput schema / properties / agent_ux

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "error": {
+      "anyOf": [
+        {},
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "meta": {
+      "additionalProperties": {},
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "next": {
+      "items": {},
+      "type": "array"
+    },
+    "payment": {
+      "additionalProperties": false,
+      "properties": {
+        "execution_status": {
+          "enum": [
+            "not_started",
+            "succeeded",
+            "failed",
+            "unknown"
+          ],
+          "type": "string"
+        },
+        "status": {
+          "enum": [
+            "not_required",
+            "required",
+            "settled",
+            "failed",
+            "unknown"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "status",
+        "execution_status"
+      ],
+      "type": "object"
+    },
+    "result": {},
+    "status": {
+      "enum": [
+        "succeeded",
+        "failed",
+        "partial",
+        "outcome_unknown"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "result",
+    "error",
+    "meta",
+    "payment",
+    "next"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / error

Added value: +{
+  "anyOf": [
+    {},
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / meta

Added value: +{
+  "additionalProperties": {},
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

addedOutput schema / properties / next

Added value: +{
+  "items": {},
+  "type": "array"
+}

addedOutput schema / properties / payment

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "execution_status": {
+      "enum": [
+        "not_started",
+        "succeeded",
+        "failed",
+        "unknown"
+      ],
+      "type": "string"
+    },
+    "status": {
+      "enum": [
+        "not_required",
+        "required",
+        "settled",
+        "failed",
+        "unknown"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "execution_status"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / recommended_next / properties / availability
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
addedOutput schema / properties / recommended_next / properties / availability_observation
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / recommended_next / properties / condition
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / recommended_next / properties / workflow_id
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / result
```
Added value: +{}
```

addedOutput schema / properties / status

Added value: +{
+  "enum": [
+    "succeeded",
+    "failed",
+    "partial",
+    "outcome_unknown"
+  ],
+  "type": "string"
+}

Changed1 schema field changedOct 8, 2026

addedOutput schema / properties / recommended_next

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "price": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "reason": {
+      "type": "string"
+    },
+    "tool": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "tool",
+    "reason",
+    "price"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 29, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "cached": {
+      "type": "boolean"
+    },
+    "confidence": {
+      "additionalProperties": false,
+      "properties": {
+        "overall": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "overall"
+      ],
+      "type": "object"
+    },
+    "data": {
+      "additionalProperties": {},
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "data_age_seconds": {
+      "type": "number"
+    },
+    "extracted_at": {
+      "type": "string"
+    },
+    "final_url": {
+      "type": "string"
+    },
+    "provenance": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "field": {
+            "type": "string"
+          },
+          "source_type": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "field",
+          "source_type"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "success": {
+      "const": true,
+      "type": "boolean"
+    },
+    "url": {
+      "type": "string"
+    },
+    "validation": {
+      "additionalProperties": false,
+      "properties": {
+        "coercions": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "missing_fields": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "schema_valid": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "schema_valid",
+        "missing_fields",
+        "coercions"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "success",
+    "url",
+    "final_url",
+    "data",
+    "validation",
+    "confidence",
+    "provenance",
+    "cached",
+    "data_age_seconds",
+    "extracted_at"
+  ],
+  "type": "object"
+}

First observedSep 28, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations to lean on, the description carries the load well: it discloses the price ($0.01 USDC), that it uses static page data only, that it never executes page JavaScript, and that it never fabricates missing fields. These are meaningful behavioral constraints, though it omits failure behavior and provenance format details that would fully round out the disclosure.

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

Conciseness3/5

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

The core sentence is tight, specific, and front-loaded. The second paragraph, however, is a long generic routing disclaimer that repeats across the toolset and does not earn its length in tool-specific value, diluting the conciseness of the definition as a whole.

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

Completeness4/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 no explanation, and the description adds the essential context: payment, static-only extraction, and non-fabrication. Combined with the clear purpose statement, an agent has enough to invoke this tool correctly, with only minor gaps around the schema parameter's exact format.

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 0%, so the description must compensate for two undocumented parameters. The phrase 'agent-defined typed JSON shape' gestures at the schema parameter's purpose, but the url parameter is only implied and the type-mapping syntax the schema enum allows is never explained, leaving the semantics partially covered.

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

Purpose4/5

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

The opening sentence names a concrete verb (extracts), the resource (a fresh webpage), and the output form (agent-defined typed JSON with validation and per-field provenance), so the tool's function is unambiguous. It does not, however, explicitly differentiate itself from lookalike siblings such as check_url or scan_content, so the boundary is inferred rather than stated.

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

Usage Guidelines4/5

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

The 'Agent entry points' block gives explicit routing rules: direct tool for a known single capability, route_tool for comparisons, /api/discover for unclear capabilities, Agent Action Gate for risky external actions, and workflow recipes for multi-step objectives. This is strong when-to-use guidance, though it is generic ecosystem boilerplate that never names the extraction-specific alternatives an agent would weigh against this tool.

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

All DropEngine x402 Agent Services tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?