# Yoofooz API Readiness Report

## API
**Name:** ToolVet
**Docs URL:** https://toolvet.app/agents
**Domain:** toolvet.app
**Generated At:** 2026-10-25T20:36:15.346951+00:00

## Certification
**Agent Readiness Score:** 65/100
**Certification Level:** Agent-Compatible With Gaps

## Agent Commerce Readiness
**Agent Commerce Score:** 50/100
**Agent Commerce Level:** Agent Commerce Emerging

This score is separate from the core Agent Readiness Score and evaluates MCP support, scoped agent identity, machine-native payments, consumption pricing, budget controls, rate controls, deterministic errors, auditability, least-privilege security, and agent observability.

## Category Scores
- Documentation Clarity: 10
- Machine Readable Spec: 10
- Authentication Clarity: 5
- Error Handling: 10
- Rate Limit Clarity: 10
- Agent Safe Workflow Support: 0
- Sandbox Availability: 0
- Webhook Event Support: 0
- Commercial Trust: 10
- Developer Experience: 10

## Strengths
- Documentation clarity
- Machine-readable specification (OpenAPI/GraphQL/etc.)
- Error handling and status codes
- Rate-limit / quota behavior
- Commercial trust (status, SLA, compliance)
- Developer experience (SDKs, quickstart, CLI)

## Risks
- Authentication model clarity signal is partial; clearer documentation recommended.
- Agent-safe workflow primitives (idempotency, retries) signal not detected in docs.
- Sandbox / test-mode availability signal not detected in docs.
- Webhook / event support signal not detected in docs.

## Recommended Next Steps
- Strengthen: Document authentication clearly (API keys, OAuth scopes, bearer tokens, secret/publishable key handling).
- Document idempotency keys, test mode, dry runs, and safe retry semantics for agents.
- Provide a sandbox / test mode with test API keys for safe agent testing.
- Expose webhook/event docs including event types, signature verification, and retry delivery.

## Evidence Signals

### Documentation clarity
- **Source:** https://toolvet.app/openapi.json
- **Matched:** parameters, request, response
- **Evidence:** "state: up = the latest check passed; degraded = the latest check failed and the one before passed; down = two or more checks in a row failed, or it never passed; unknown = not checked yet."

- **Source:** https://toolvet.app/agents
- **Matched:** parameters, request
- **Evidence:** "...to try how paying works check an endpoint before you pay it use it as an mcp server add it to your mcp client add it to your agent framework search parameters free endpoints limits and errors machine-readable try it in 30 seconds run one search. the first 10 each day are free, so there is nothing to set..."

### Machine-readable specification (OpenAPI/GraphQL/etc.)
- **Source:** https://toolvet.app/agents
- **Matched:** openapi, json schema, endpoints, schema
- **Evidence:** "...or every scanner slot is in use. retry-after says how long to wait. 500 internal_error our side failed. nothing is charged. machine-readable /openapi.json openapi, with x402 pricing on every paid operation /llms.txt a summary for language models /.well-known/x402 the paid resources, for x402..."

- **Source:** https://toolvet.app/openapi.json
- **Matched:** openapi, schema
- **Evidence:** "{'openapi':'3.1.0','info': ,'servers':[ ],'x-discovery': ,'paths':{'/api/v1/search':{'get':{'operationid':'search','summary':'search vetted agent..."

### Authentication model clarity
- **Source:** https://toolvet.app/agents
- **Matched:** authentication, authorization, api key
- **Evidence:** "...in settings, open apps, then advanced settings, and turn on developer mode. click create app, enter a name and the server url below, and select no authentication. confirm that you trust the app, then click create. in a chat, select developer mode from the + menu and turn the app on. https://toolvet.app/mcp..."

- **Source:** https://toolvet.app/mcp-scanner
- **Matched:** api key, keys
- **Evidence:** "...to steer the agent. we never call a tool. mcp server url scan the streamable http endpoint, often ending in /mcp. don't paste a url that contains an api key or token: the link to the report includes the url. try an example: toolvet's own mcp server on this page what it looks for an example how the grade..."

### Error handling and status codes
- **Source:** https://toolvet.app/openapi.json
- **Matched:** 400, 403, 404, 409, 429, 500
- **Evidence:** "state: up = the latest check passed; degraded = the latest check failed and the one before passed; down = two or more checks in a row failed, or it never passed; unknown = not checked yet."

- **Source:** https://toolvet.app/agents
- **Matched:** 400, 404, 429, 500, retry, errors
- **Evidence:** "...header. no funds move yet. we verify the signature, answer the request, and settle the payment only for a successful answer. any answer with status 400 or above settles nothing. any x402 client does this for you. keep the paying wallet small (a few dollars of usdc on base) and separate from your..."

### Rate-limit / quota behavior
- **Source:** https://toolvet.app/agents
- **Matched:** rate limit, retry-after, 429, limits
- **Evidence:** "...in usdc, per call. you are only charged when the request succeeds: a 4xx answer (unknown id, missing parameter) settles nothing. paid calls are not rate limited per ip. free to try the first 10 searches each day are free, so you can see real results before you add a wallet. they are counted per ip address..."

- **Source:** https://toolvet.app/openapi.json
- **Matched:** rate limit, 429
- **Evidence:** "state: up = the latest check passed; degraded = the latest check failed and the one before passed; down = two or more checks in a row failed, or it never passed; unknown = not checked yet."

### Commercial trust (status, SLA, compliance)
- **Source:** https://toolvet.app/agents
- **Matched:** status page, uptime, support, changelog, security
- **Evidence:** "...mcp get_service get /api/v1/services/ /status is it up: state, since when, latest check, 30-day uptime and recent outages. the same as the listing's status page at /status/ , from stored checks, with no live probe. mcp get_service_status get /api/v1/watch?ids= outages, recoveries, and price and pay-to..."

- **Source:** https://toolvet.app/c/security-trust
- **Matched:** uptime, changelog, security
- **Evidence:** "...agent trust receipt ai-akari.ai read-only remote mcp for externally grounded ai agent trust receipts. mcp server security & trust 2 tools open 100% uptime, 279 ms passing, checked 10 h ago 90 trust boundaryai boundaryai.ai deterministic runtime safety for ai agents: scan pii, gate tool actions, verify..."

### Developer experience (SDKs, quickstart, CLI)
- **Source:** https://toolvet.app/agents
- **Matched:** sdk, cli
- **Evidence:** "...a day. mcp server add it to claude code, claude (web and desktop), cursor, vs code and chatgpt. agent framework four tools for the vercel ai sdk, langchain or the openai agents sdk. on this page try it in 30 seconds prices free to try how paying works check an endpoint before you pay it use..."

- **Source:** https://toolvet.app/c/security-trust
- **Matched:** cli
- **Evidence:** "...at a published price, paid by x402 or card mcp server security & trust 5 tools open 100% uptime, 214 ms passing, checked 4 h ago 90 trust criora climate risk criora.com climate and disaster risk for any place: warnings, floods, heat, storms, quakes, countries, map mcp server security & trust 15..."

## AI Analyst Summary
_Provider: nvidia | Model: nvidia/nemotron-3.5-super-vl-120b-a12b_

ToolVet scores 65/100 for agent readiness with Agent-Compatible With Gaps certification. Core documentation, specs, and developer experience are strong, but authentication clarity, agent-safe workflows, sandbox availability, and webhook support are missing. Remediation is needed before agents can safely integrate at production scale.

**Credibility Notes:**
- Documentation clarity, machine-readable spec, error handling, rate limits, commercial trust, and developer experience all score 10/10.
- Authentication clarity scores only 5/10, indicating partial and unclear auth documentation.
- Agent-safe workflow support, sandbox availability, and webhook event support score 0/10, signaling critical gaps for autonomous agents.

**Next Actions:**
- Document authentication model clearly including API keys, OAuth scopes, bearer tokens, and secret/publishable key handling.
- Add idempotency keys, test mode, dry runs, and safe retry semantics for agent workflows.
- Provide a sandbox/test mode with test API keys and publish webhook event documentation with signature verification and retry delivery.

## Yoofooz Summary
This API has been evaluated for autonomous AI-agent usability. The score reflects documentation quality, machine-readable specification signals, authentication clarity, error handling, workflow safety, commercial trust, and developer experience.