x402 Bazaar

ai_extract_batch

Read-onlyIdempotent

Same fields across up to 10 texts, one payment — The pipeline version of ai-extract: send up to 10 documents (text1=…&text2=… or texts= with ||| separators) and one field list — get one schema-enforced JSON object per document, in order, from a single paid call. 10 extractions for $0.10 instead of 10x the per-call overhead: built for agents parsing feeds, inboxes, scrape batches and receipt piles. Up to 6K chars per document. Required input: text1. Priced $0.10 per call over x402 on Base; send a prepaid x-credit-token header for unlimited calls, or get 1 free call/day per tool. No wallet or API key required.

Input Schema

TableJSON Schema

Name	Required	Description
`text1`	Yes	Document 1
`text2`	No	Document 2 (optional)
`fields`	No	Fields (comma-separated)

Output Schema

TableJSON Schema

Name	Required	Description
`data`	No	The result payload. Shape is service-specific; every field is documented in the tool description.
`service`	No	The service id that answered.
`checkedAt`	No	ISO-8601 timestamp of when the underlying reads were taken.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedAug 31, 2026

changedOutput schema / properties / data / description

Previous value: -"The result payload. Shape is service-specific; every field is documented in the service description above."New value: +"The result payload. Shape is service-specific; every field is documented in the tool description."

Changed1 schema field changedAug 31, 2026
- removedOutput schema / required
```
Removed value: -[
-  "data"
-]
```
AddedAug 30, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description adds substantial behavioral detail beyond the readOnly/idempotent annotations: one schema-enforced JSON object per document returned in order, 6K character limit, single paid call, prepaid credit header, one free call per day, and no wallet/API key requirement. These details give an agent actionable expectations without contradicting annotations.

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

Conciseness5/5

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

The description is dense but every sentence earns its place: core behavior, batching mechanism, output shape, cost model, limits, required input, and authentication are all covered. The most important purpose and differentiator are front-loaded, and no filler is present.

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?

Given the tool's batch complexity, the description covers input limits, multi-document formatting, output ordering and schema enforcement, payment model, and access requirements. An output schema exists, so the description does not need to spell out return field details. The agent has everything needed to select and invoke the tool correctly.

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

Parameters4/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 parameters. The description goes further by explaining practical usage: text1=…&text2=…, texts= with ||| separators, one shared field list, and per-document character limits. This adds real value beyond the raw schema.

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 description states a clear verb and resource: batch extraction over multiple documents. It explicitly identifies itself as 'The pipeline version of ai-extract' and contrasts its behavior (up to 10 texts, one field list, one payment) with the sibling tool, making differentiation easy.

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 description gives solid context for when to use the tool: same fields across up to 10 documents, built for feeds, inboxes, scrape batches, and receipt piles. It names the sibling alternative ai-extract, though it does not explicitly spell out when-not-to-use cases such as handling more than 10 documents or per-document differing fields.

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

All x402 Bazaar tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0

Disambiguation2/5

Despite excellent per-tool descriptions, the set contains many near-overlapping tools: rug_score, batch_risk, pre_trade_gate, and deep_dd all assess token risk; wallet_portfolio, wallet_networth, and wallet_tokens all list balances; b20_safety, b20_gate, and b20_dossier overlap heavily; url_extract, web_extract, ai_extract, and url_to_json also blur boundaries. An agent would struggle to consistently pick the right tool without reading every description.

Naming Consistency4/5

Naming is overwhelmingly consistent snake_case verb_noun (token_price, rug_score, address_trust, file_convert, safe_to_send). Minor deviations: noun-only names like holders, basename, deep_dd, business_days, and new_tokens, plus the abbreviation deep_dd, slightly break the pattern.

Tool Count1/5

137 tools is far beyond the 50+ extreme-mismatch threshold. Even as a marketplace bazaar, this is an enormous, unwieldy surface where many tools overlap and each contributes only a sliver of unique value.

Completeness4/5

For the apparent purpose — a pay-per-call bazaar covering on-chain analysis, wallet intelligence, token due diligence, plus generic text/web/finance utilities — the surface is extensive and covers most read-only workflows with few dead ends. Minor gaps exist (no historical price series, no swap execution, no true on-chain write actions), but the set is not severely incomplete for its stated niche.

Resources

Need Help?