x402basequality 0.45

Pay-per-query contextual search across crypto, company, and insurance verticals via x402 on Base.

Price
0.1 USDC / call
Protocol
x402
Verified
no

What it does

Kirha's /search endpoint is an x402-enabled API that lets agents and developers ask natural-language questions and receive structured context drawn from curated "S-tier" data providers. The endpoint accepts a POST with a search query and a vertical identifier (one of "crypto", "company", or "insurance") and returns a JSON response containing a summary, raw data, and planning objects.

Payment is handled via the x402 protocol on the Base network using USDC (contract 0x8335…2913). The maximum cost per request is 0.10 USDC (100,000 base units at 6 decimals), making it a micro-payment-friendly, pay-per-data-point service. The endpoint advertises a maximum timeout of 120 seconds, suggesting that queries may involve real-time aggregation or LLM-based summarization behind the scenes.

Documentation beyond the x402 challenge itself is essentially absent — the provider's root domain, /docs, /api, /pricing, and /README all return 404. The only supplementary reference is the provider list at https://app.kirha.com/providers, mentioned in the challenge description. Because of this, details about rate limits, supported query complexity, response size, and the exact data sources behind each vertical are unknown and must be discovered experimentally.

Capabilities

natural-language-searchcrypto-datacompany-datainsurance-datax402-paymentusdc-basepay-per-querystructured-context

Use cases

  • An AI agent researching a cryptocurrency project pays per query to get a structured summary and raw data.
  • A financial analyst tool queries company-vertical context to enrich due-diligence reports.
  • An insurance comparison agent fetches structured context about policies or carriers on demand.
  • A chatbot integrates Kirha search to answer user questions about crypto, companies, or insurance with sourced data.

Fit

Best for

  • AI agents that need on-demand, pay-per-call contextual search without subscriptions
  • Developers building crypto, company, or insurance research tools
  • Workflows requiring structured summaries plus raw data from curated providers

Not for

  • High-volume bulk data ingestion (pay-per-query at $0.10 adds up quickly)
  • Use cases outside the three supported verticals (crypto, company, insurance)
  • Users who need detailed API documentation or SLA guarantees before integrating

Quick start

curl -X POST http://x402.kirha.com/search \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402_payment_token>" \
  -d '{"query": "What is the current market cap of Ethereum?", "verticalId": "crypto"}'

Example

Request

{
  "query": "What is the current market cap of Ethereum?",
  "verticalId": "crypto"
}

Response

{
  "id": "abc123-def456",
  "summary": "Ethereum (ETH) currently has a market capitalization of approximately $XXX billion, making it the second-largest cryptocurrency by market cap.",
  "planning": {
    "steps_taken": [],
    "providers_queried": []
  },
  "raw_data": {
    "symbol": "ETH",
    "sources": [],
    "market_cap_usd": 0
  }
}

Endpoint

Transporthttp
Protocolx402
Pay to0x46c52aA3823488EfD7F7e0dAB066976419292e6e
CurrencyUSD COIN

Quality

0.45/ 1.00

The x402 challenge is live and provides a clear input/output schema with three verticals and USDC pricing on Base. However, there is zero external documentation — no docs page, no OpenAPI spec, no README, and no crawlable content beyond the challenge itself. The response schema fields (raw_data, planning) are opaque objects with no further specification. Score reflects a working endpoint with useful schema but very sparse documentation.

Warnings

  • No documentation available: /docs, /api, /pricing, and /README all return 404.
  • Response schema fields 'raw_data' and 'planning' are typed as generic objects with no further specification.
  • The example response JSON is inferred from the output schema and may not reflect actual response structure.
  • No information available about rate limits, uptime SLA, or data freshness guarantees.
  • The provider list at https://app.kirha.com/providers was not crawled; actual data sources are unknown.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-18 20:16:02Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-22

Agent access