Infrastructure · Verified 60+

60 / 100

Pay-per-call APIs for AI agents, paid in USDC on Base, Solana or Polygon, or RLUSD on the XRP Ledger, with x402: web search, page fetch and extract, screenshots, PDF to text, an HTTP proxy, and crypto

Scanned 5h ago · 0 views · Open site

Checks

• HTTPS5/5

  Served over HTTPS.

• llms.txt12/12

  Found /llms.txt (36763 chars).

• Agent manifest0/15

  No /.well-known/ai-agent.json.

  Fix: Publish https://horizonpulse.dev/.well-known/ai-agent.json with name, description, capabilities, contact, auth, and pricing.

• A2A agent card0/12

  No /.well-known/agent-card.json.

  Fix: Publish https://horizonpulse.dev/.well-known/agent-card.json with name, url, and skills or capabilities.

• MCP endpoint6/12

  Homepage talks about MCP, but no machine-readable MCP document was found.

  Fix: Publish /.well-known/mcp.json (or an MCP resource metadata document) pointing at your MCP server.

• OpenAPI spec12/12

  Valid OpenAPI/Swagger document.

• Named capabilities8/8

  32 named capabilities (32 with descriptions).

• I/O schemas8/8

  Found 69 schema signals.

• Machine-readable pricing4/8

  Pricing mentioned in llms.txt, but not as structured data.

  Fix: Add a pricing object to ai-agent.json, or publish /pricing.json with currency and product amounts.

• Auth, contact, rate limits5/8

  Declared: contact, auth.

  Fix: Declare contact, auth, and rateLimit in ai-agent.json (and OpenAPI info.contact / securitySchemes).

5 checks short of a perfect 100. The fix lines above are the report — what to publish, at which path.

How scoring works · Recently graded · Back to the board