# Yoofooz API Readiness Report

## API
**Name:** Firecrawl
**Docs URL:** https://docs.firecrawl.dev/introduction
**Domain:** docs.firecrawl.dev
**Generated At:** 2026-10-26T02:22:50.596619+00:00

## Certification
**Agent Readiness Score:** 90/100
**Certification Level:** Yoofooz Certified

## 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: 10
- Error Handling: 10
- Rate Limit Clarity: 10
- Agent Safe Workflow Support: 10
- Sandbox Availability: 0
- Webhook Event Support: 10
- Commercial Trust: 10
- Developer Experience: 10

## Strengths
- Documentation clarity
- Machine-readable specification (OpenAPI/GraphQL/etc.)
- Authentication model clarity
- Error handling and status codes
- Rate-limit / quota behavior
- Agent-safe workflow primitives (idempotency, retries)
- Webhook / event support
- Commercial trust (status, SLA, compliance)
- Developer experience (SDKs, quickstart, CLI)

## Risks
- Sandbox / test-mode availability signal not detected in docs.

## Recommended Next Steps
- Provide a sandbox / test mode with test API keys for safe agent testing.

## Evidence Signals

### Documentation clarity
- **Source:** https://docs.firecrawl.dev/api-reference/v2-openapi.json
- **Matched:** parameters, request, response, examples, docs, reference
- **Evidence:** "...[ ], 'paths': { '/monitor': { 'post': { 'summary': 'create a monitor', 'operationid': 'createmonitor', 'tags': [ 'monitoring' ], 'security': [ ], 'requestbody': { 'required': true, 'content': { 'application/json': { 'schema': , 'examples': { 'scrapemonitor': { 'summary': 'scrape a url every 30..."

- **Source:** https://docs.firecrawl.dev/rate-limits
- **Matched:** request, response, examples, docs, reference
- **Evidence:** "rate limits for different pricing plans and api requests copy page copy page rate limits cap how many requests your team can make per minute, while concurrency limits cap how many jobs can run in..."

### Machine-readable specification (OpenAPI/GraphQL/etc.)
- **Source:** https://docs.firecrawl.dev/api-reference/errors
- **Matched:** json schema, endpoints, schema, endpoint reference
- **Evidence:** "...size. reduce the payload (e.g. shorter schema, fewer urls per batch). no 422 unprocessable entity / extraction schema error schema is invalid json schema, or the model could not produce a conforming result. validate the schema; loosen required fields; try a different model . sometimes 429 rate limit..."

- **Source:** https://docs.firecrawl.dev/es/api-reference/errors
- **Matched:** json schema, endpoints, schema
- **Evidence:** "...útil (p. ej., con un esquema más corto o menos urls por lote). no 422 unprocessable entity / error en el esquema de extracción el esquema no es un json schema válido o el modelo no pudo generar un resultado que se ajuste al esquema. valida el esquema; reduce los campos obligatorios; prueba con otro model ...."

### Authentication model clarity
- **Source:** https://docs.firecrawl.dev/mcp-server/keyless
- **Matched:** bearer token, oauth, authorization, api key
- **Evidence:** "agents can start instantly, no api key required. add an api key to unlock more usage. copy page copy page try keyless keyless mcp is rate limited and exposes search, scrape, and parse...."

- **Source:** https://docs.firecrawl.dev/mcp-server
- **Matched:** bearer token, oauth, api key
- **Evidence:** "...this is a server url for your mcp client, not a page to open directly in a browser. api-key connections use https://mcp.firecrawl.dev/v2/mcp with a bearer token instead; see add an api key . client setup for agents start keyless or use an api key. for humans sign in via browser. using github copilot? follow..."

### Error handling and status codes
- **Source:** https://docs.firecrawl.dev/api-reference/errors
- **Matched:** error codes, 400, 401, 403, 404, 409, 429, 500, retry, errors
- **Evidence:** "...to use a partial and continue the run. in the trace, the same outcome appears as a run.finished event with outcome: 'credit_limit_reached' . trace error codes terminal and error.occurred trace events carry a structured error object whose code is one of five values. each also carries a retryable boolean,..."

- **Source:** https://docs.firecrawl.dev/api-reference/v2-openapi.json
- **Matched:** idempotency, 400, 401, 403, 404, 409, 429, 500, retry, errors
- **Evidence:** "...options (400); the only allowed sibling keys are `timeout`, `origin`, and `integration`. use the `x-request-id` request header as a client-chosen idempotency key (1 to 128 characters of letters, digits, `.`, `_`, `:`, `-`) — it is echoed back, and a completed request with the same key replays its original..."

### Rate-limit / quota behavior
- **Source:** https://docs.firecrawl.dev/api-reference/errors
- **Matched:** rate limit, rate limits, retry-after, too many requests, 429, limits
- **Evidence:** "...json schema, or the model could not produce a conforming result. validate the schema; loosen required fields; try a different model . sometimes 429 rate limit exceeded too many requests for your plan’s per-minute limit. back off and retry after retry-after seconds. see rate limits . yes, with backoff 429..."

- **Source:** https://docs.firecrawl.dev/rate-limits
- **Matched:** rate limit, rate limits, 429, limits
- **Evidence:** "rate limits for different pricing plans and api requests copy page copy page rate limits cap how many requests your team can make per minute, while concurrency..."

### Agent-safe workflow primitives (idempotency, retries)
- **Source:** https://docs.firecrawl.dev/api-reference/v2-openapi.json
- **Matched:** idempotency, idempotency key
- **Evidence:** "...options (400); the only allowed sibling keys are `timeout`, `origin`, and `integration`. use the `x-request-id` request header as a client-chosen idempotency key (1 to 128 characters of letters, digits, `.`, `_`, `:`, `-`) — it is echoed back, and a completed request with the same key replays its original..."

### Webhook / event support
- **Source:** https://docs.firecrawl.dev/webhooks/security
- **Matched:** webhooks, event types, signature verification, webhook
- **Evidence:** "..., express . raw ( )); app . post ( '/webhook/firecrawl' , ( req , res ) => { const signature = req . get ( 'x-firecrawl-signature' ); const webhooksecret = process . env . firecrawl_webhook_secret ; if ( ! signature || ! webhooksecret ) // extract hash from signature header const [ algorithm ,..."

- **Source:** https://docs.firecrawl.dev/webhooks/events
- **Matched:** webhook, events
- **Evidence:** "webhook event reference copy page copy page firecrawl sends webhook events at each stage of a job’s lifecycle, so you can track progress, capture results,..."

### Commercial trust (status, SLA, compliance)
- **Source:** https://docs.firecrawl.dev/security
- **Matched:** soc 2, trust center, support, security, compliance
- **Evidence:** "...security or procurement team asks before approving firecrawl. to explore them, reach out to our team on the enterprise page . compliance and reports soc 2 type ii : our soc 2 type ii audit is in progress. trust center : the firecrawl trust center lists our compliance status and controls. you can..."

- **Source:** https://docs.firecrawl.dev/introduction
- **Matched:** uptime
- **Evidence:** "...and more. handles the hard stuff : proxies, anti-bot, javascript rendering, and dynamic content. reliable : built for production with high uptime and consistent results. fast : results in seconds, optimized for high throughput. mcp server : connect firecrawl to any ai tool via the model..."

### Developer experience (SDKs, quickstart, CLI)
- **Source:** https://docs.firecrawl.dev/es/api-reference/errors
- **Matched:** sdk, cli, dashboard
- **Evidence:** "...v2 español buscar... ⌘ k status support sign up firecrawl/firecrawl firecrawl/firecrawl buscar... navigation uso de la api errores documentación sdks referencia de la api crear con ia playground blog comunidad registro de cambios uso de la api introducción errores endpoints de búsqueda post..."

- **Source:** https://docs.firecrawl.dev/rate-limits
- **Matched:** sdk, cli
- **Evidence:** "...scrape, and parse without an api key. other hosted mcp tools require an account connection or an api key. for official firecrawl clients, the cli, sdks, and rest api, keyless access also includes interact . on firecrawl cloud, research, developer, and government search endpoints can also be used..."

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

Firecrawl achieves a 90% agent readiness score and is Yoofooz Certified, excelling across documentation, authentication, and webhook support. The only critical gap is the absence of a sandbox or test mode for safe agent testing. Resolving this would position the API for full production agent deployment.

**Credibility Notes:**
- Perfect category scores in documentation, spec, auth, errors, rate limits, webhooks, trust, and DX.
- Missing sandbox/test-mode signal drops sandbox availability to 0.
- Certified status reflects strong commercial trust and compliance posture.

**Next Actions:**
- Add a sandbox or test mode with dedicated test API keys.
- Publish clear sandbox documentation and reset behavior for agents.
- Re-scan after sandbox launch to validate full readiness.

## 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.