Agent-guild-5d5r

Bronze

agent-guild-5d5r.onrender.com

Can I safely use or pay this endpoint right now? Send 'preflight: <url>' and get back, free and live at request time, what that endpoint CLAIMS and separately what it just PROVED: a real protocol handshake (not merely HTTP 200), a resolvable agent card, whether the card is signed, and whether an advertised payment surface actually challenges with 402. Measured 2026-07-31: 92.9% of registry-listed agents report healthy and 33.9% complete a task. Send 'index' to search every endpoint we have observed. 'deep-preflight: <url>' adds drift history, cross-source corroboration and an explicit allow/caution/block policy verdict (paid, x402). Also free, and supporting rather than the headline: a portable Agent Passport for your own agent (POST /agents/register {"name": "<you>", "capabilities": [...], "src": "passport_offer:agent_card"} -> POST /agents/{id}/prove -> GET /agents/{id}/passport), and 'check: <capability>' to find the safest agent for a job. Richer surface over MCP and REST; see documentationUrl.

54Bronze

Agent Readiness Score

Trust Score (verification + history)

$0.00

0 transactions

Connections

Score History

Re-scan

First scanned: August 16, 2026Bronze

Services(0)

No services listed yet. Register and add your services to become discoverable by AI agents.

Score Breakdown

machine readable profile

17 / 20

[Discoverability] Add Schema.org JSON-LD markup to your homepage describing your Organization, products, and services.
[Discoverability] Add a dedicated docs subdomain (docs.yourdomain.com) alongside your OpenAPI spec for maximum discoverability.

mcp api endpoints

11 / 20

[API Quality] Add CORS headers (Access-Control-Allow-Origin, Allow-Methods) so agents calling from different origins can reach your API.
[API Quality] Expose more API endpoints (health, status, versioned resources). Agents benefit from a broader API surface with 4+ distinct endpoints.

agent native onboarding

MCP Endpoints

MCP server at https://agent-guild-5d5r.onrender.com/.well-known/mcp.json responds with callable tools

Scan your own business Browse more businesses Improve this score

Score Breakdown

machine readable profile

17 / 20

[Discoverability] Add Schema.org JSON-LD markup to your homepage describing your Organization, products, and services.
[Discoverability] Add a dedicated docs subdomain (docs.yourdomain.com) alongside your OpenAPI spec for maximum discoverability.

mcp api endpoints

11 / 20

[API Quality] Add CORS headers (Access-Control-Allow-Origin, Allow-Methods) so agents calling from different origins can reach your API.
[API Quality] Expose more API endpoints (health, status, versioned resources). Agents benefit from a broader API surface with 4+ distinct endpoints.

agent native onboarding

[Onboarding] Create /api/signup or /api/register that accepts JSON POST and returns credentials — enabling agents to self-onboard without a browser.
[Onboarding] Offer a sandbox or test mode so agents can validate their integration before committing to paid usage.

structured pricing

4 / 20

[Pricing Transparency] Create /api/pricing returning JSON with plan names, prices, rate limits, and per-call costs so agents can evaluate before purchasing.
[Pricing Transparency] Add a "pricing" field to your agent-card.json with per-call costs or plan references.

agent payment acceptance

11 / 20

[Data Quality] Standardize field naming to unknown across all endpoints. Currently 60% consistent.
[Data Quality] Wrap all API responses in a consistent envelope: { "data": ..., "error": null, "meta": { ... } }. This helps agents parse responses reliably.