# Yoofooz API Readiness Report

## API
**Name:** Clerk APIs
**Docs URL:** https://clerk.com/docs/reference/api/overview
**Domain:** clerk.com
**Generated At:** 2026-10-05T21:05:20.746894+00:00

## Certification
**Agent Readiness Score:** 70/100
**Certification Level:** Yoofooz Ready

## Agent Commerce Readiness
**Agent Commerce Score:** 20/100
**Agent Commerce Level:** Agent Commerce Not Yet Detected

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: 0
- Agent Safe Workflow Support: 0
- Sandbox Availability: 0
- Webhook Event Support: 10
- Commercial Trust: 10
- Developer Experience: 10

## Strengths
- Documentation clarity
- Machine-readable specification (OpenAPI/Swagger)
- Authentication model clarity
- Error handling and status codes
- Webhook / event support
- Commercial trust (status, SLA, compliance)
- Developer experience (SDKs, quickstart, CLI)

## Risks
- Rate-limit / quota behavior signal not detected in docs.
- Agent-safe workflow primitives (idempotency, retries) signal not detected in docs.
- Sandbox / test-mode availability signal not detected in docs.

## Recommended Next Steps
- Document rate limits, quota behavior, 429 responses, and Retry-After guidance.
- 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.

## Evidence Signals

### Documentation clarity
- **Source:** https://clerk.com/docs/reference/api/overview
- **Matched:** quickstart, request, response, docs, guide, reference, overview
- **Evidence:** "...hildren\':[[\'precomputecode\',\'~\',\'d\',[\'navigation\',\'api\',\'atlas-public-chat\',\'feedback\',\'images\',\'links.json\',\'llms.txt\',\'md\',\'quickstart-prompt\',\'raw\',\'reference\',\'revalidate\',\'search.json\',\'search.md\']],{\'children\':[[\'slugsegments\',\'reference/api/overview\',\'oc\',[\'s..."

- **Source:** https://clerk.com/react-authentication
- **Matched:** quickstart, response, docs, guide
- **Evidence:** "...with a developer-friendly react interface. you can use our components out of the box or fully customize them to match your ui. refer to the quickstart guide to get started. how easy is it to install and configure clerk’s react sdk? run npm install @clerk/react , set up your clerk publishable key as..."

### Machine-readable specification (OpenAPI/Swagger)
- **Source:** https://clerk.com/docs/reference/frontend-api
- **Matched:** openapi, endpoints, schema
- **Evidence:** "...6fyykrkrhktc.js\',\'/_next/static/immutable/chunks/11jzb72s-pyc3.js\',\'/_next/static/immutable/chunks/00badjw1wz37s.js\'],\'fapiscalar\']\n43:t97910,openapi: 3.0.3\ninfo:\n title: clerk frontend api\n version: v1\n description: \u003e-\n the clerk rest frontend api, meant to be accessed from a browser or..."

- **Source:** https://clerk.com/docs/reference/backend-api
- **Matched:** openapi, endpoints, schema
- **Evidence:** "...6fyykrkrhktc.js\',\'/_next/static/immutable/chunks/11jzb72s-pyc3.js\',\'/_next/static/immutable/chunks/00badjw1wz37s.js\'],\'bapiscalar\']\n42:tc0c65,openapi: 3.0.3\ninfo:\n title: clerk backend api\n x-logo:\n url: https://clerk.com/_next/image?url=%2fimages%2fclerk-logo.svg\u0026w=96\u0026q=75\n..."

### Authentication model clarity
- **Source:** https://clerk.com/docs/reference/frontend-api
- **Matched:** oauth, access token, client secret, scopes, authentication, authorization, api key, keys
- **Evidence:** "...endpoints like jwks, deep linking, and openid-configuration.\n - name: health\n description: used to get the health status of the api.\n - name: oauth2 identity provider\n description: requests for the oauth2 authorization flow.\n - name: oauth2 callbacks\n description: used to receive callbacks..."

- **Source:** https://clerk.com/docs/reference/backend-api
- **Matched:** oauth, access token, publishable key, authentication, authorization, api key, keys
- **Evidence:** "...enabling you to integrate with third-party\n services.\n externaldocs:\n url: https://clerk.com/docs/request-authentication/jwt-templates\n - name: oauth applications\n description: oauth applications contain data for clients using clerk as an\n oauth2 identity provider.\n - name: oauth access..."

### Error handling and status codes
- **Source:** https://clerk.com/docs/reference/backend-api
- **Matched:** 400, 401, 403, 404, 409, 500, errors
- **Evidence:** "...whether to use the domain for the script url\n schema:\n type: boolean\n responses:\n \'200\':\n description: the interstitial page markup\n \'400\':\n description: a required query parameter is missing\n \'500\':\n description: an infinite redirect loop was detected\n /jwks:\n get:\n..."

- **Source:** https://clerk.com/docs/reference/frontend-api
- **Matched:** 400, 401, 403, 404, 500, errors
- **Evidence:** "...or an oauth\n error.\n\n an invalid `resource` returns `error=invalid_target`. the redirect\n preserves a supplied `state` and includes `iss`.\n \'400\':\n description: direct bad-request response used when the authorization server\n cannot safely return the error to the client's redirect uri.\n..."

### Agent-safe workflow primitives (idempotency, retries)
- **Source:** https://clerk.com/docs/reference/frontend-api
- **Matched:** metadata
- **Evidence:** "...\'#/components/responses/wellknown.openidconfiguration\'\n /.well-known/oauth-authorization-server:\n get:\n summary: oauth 2.0 authorization server metadata\n description: get the oauth 2.0 authorization server metadata according to rfc 8414\n operationid: getoauth2authorizationservermetadata\n security:..."

### Webhook / event support
- **Source:** https://clerk.com/docs/reference/backend-api
- **Matched:** webhooks, webhook, events
- **Evidence:** "...a user that has successfully signed up\n to your application.\n externaldocs:\n url: https://clerk.com/docs/references/javascript/user\n - name: webhooks\n description: you can configure webhooks to be notified about various events that\n happen on your instance.\n externaldocs:\n url:..."

- **Source:** https://clerk.com/docs/reference/frontend-api
- **Matched:** callback, subscriptions
- **Evidence:** "...to get the health status of the api.\n - name: oauth2 identity provider\n description: requests for the oauth2 authorization flow.\n - name: oauth2 callbacks\n description: used to receive callbacks from successful oauth attempts.\n - name: saml\n description: used in authentication flows using saml.\n -..."

### Commercial trust (status, SLA, compliance)
- **Source:** https://clerk.com/user-authentication
- **Matched:** soc 2, support, changelog, security, compliance
- **Evidence:** "...flow. all out-of-the-box. build with agents ❯ add clerk auth to my app: clerk.com/skill.md add clerk auth to my app: clerk.com/skill.md soc 2 your customer data is protected to the highest security and compliance standards. hipaa hipaa-compliant for safely storing your most sensitive user..."

- **Source:** https://clerk.com/docs/reference/api/overview
- **Matched:** support, changelog, security
- **Evidence:** "...privacy policy website terms of use security legal resources do not sell or share my personal information cookie manager © 2026 clerk, inc. support copy as markdown copy as markdown..."

### Developer experience (SDKs, quickstart, CLI)
- **Source:** https://clerk.com/docs/reference/api/overview
- **Matched:** quickstart, sdk, cli, guides, dashboard
- **Evidence:** "...hildren\':[[\'precomputecode\',\'~\',\'d\',[\'navigation\',\'api\',\'atlas-public-chat\',\'feedback\',\'images\',\'links.json\',\'llms.txt\',\'md\',\'quickstart-prompt\',\'raw\',\'reference\',\'revalidate\',\'search.json\',\'search.md\']],{\'children\':[[\'slugsegments\',\'reference/api/overview\',\'oc\',[\'s..."

- **Source:** https://clerk.com/docs/reference/api/overview.md
- **Matched:** sdk, cli, guides
- **Evidence:** "# api reference while accessing clerk functionality via sdk is the easiest path, clerk offers three different http apis for you to interact with directly. [the clerk frontend..."

## AI Analyst Summary
AI analysis unavailable: no analysis available

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