# Yoofooz API Readiness Report

## API
**Name:** FDIC BankFind Suite
**Docs URL:** https://api.fdic.gov/banks/docs
**Domain:** api.fdic.gov
**Generated At:** 2026-10-25T22:50:01.603622+00:00

## Certification
**Agent Readiness Score:** 40/100
**Certification Level:** Not Yet Agent-Ready

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

## Strengths
- Documentation clarity
- Machine-readable specification (OpenAPI/GraphQL/etc.)
- Error handling and status codes

## Risks
- Authentication model clarity signal is partial; clearer documentation recommended.
- 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.
- Webhook / event support signal not detected in docs.
- Commercial trust (status, SLA, compliance) signal is partial; clearer documentation recommended.
- Developer experience (SDKs, quickstart, CLI) signal not detected in docs.

## Recommended Next Steps
- Strengthen: Document authentication clearly (API keys, OAuth scopes, bearer tokens, secret/publishable key handling).
- 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.
- Expose webhook/event docs including event types, signature verification, and retry delivery.
- Strengthen: Publish status page, SLA, and security/compliance posture (SOC 2, GDPR, PCI as applicable).
- Provide SDKs / client libraries, quickstarts, CLI tools, and runnable code samples.

## Evidence Signals

### Documentation clarity
- **Source:** https://api.fdic.gov/banks/docs/swagger.yaml
- **Matched:** parameters, request, response, examples
- **Evidence:** "...- apikeyauth: [] summary: get financial institutions operationid: searchinstitutions description: returns a list of financial institutions. parameters: - in: query name: api_key description: api key used for api.fdic.gov required: false schema: type: string - in: query name: filters description: |..."

- **Source:** https://api.fdic.gov/banks/docs
- **Matched:** response, examples, overview
- **Evidence:** "...a '*' dateupdt:[2010-01-01 to *] output formats data output is available as json or csv. the format is controlled by the accept header. see the responses section in the interactive documentation below for examples. api endpoints"

### Machine-readable specification (OpenAPI/GraphQL/etc.)
- **Source:** https://api.fdic.gov/banks/docs
- **Matched:** openapi, swagger, api spec, endpoints
- **Evidence:** "...common financial reports (.xlsx spreadsheet) api documentation see interactive documentation available below to provide an overview of the api. full openapi specification (formerly known as swagger) for the api filter syntax the api uses the elastic search query string syntax for filtering. some notes on..."

- **Source:** https://api.fdic.gov/banks/docs/swagger.yaml
- **Matched:** openapi, schema
- **Evidence:** "openapi: 3.0.0 servers: - description: api to serve banking industry data to the public. url: '/banks' info: description: api to serve banking industry data..."

### Authentication model clarity
- **Source:** https://api.fdic.gov/banks/docs
- **Matched:** api key, keys
- **Evidence:** "...using this data. everything you need to integrate with this api is available below. more data will be added to the portal on an ongoing basis. api keys many public apis use keys as a way to secure and monitor api usage, and bankfind suite follows this best practice. users are currently not required..."

- **Source:** https://api.fdic.gov/banks/docs/swagger.yaml
- **Matched:** api key
- **Evidence:** "...operationid: searchinstitutions description: returns a list of financial institutions. parameters: - in: query name: api_key description: api key used for api.fdic.gov required: false schema: type: string - in: query name: filters description: | the filter for the bank search. all values must..."

### Error handling and status codes
- **Source:** https://api.fdic.gov/banks/docs/swagger.yaml
- **Matched:** 400, 500
- **Evidence:** "...$ref: '#/components/schemas/metadata' data: type: array items: $ref: '#/components/schemas/institution' text/csv: schema: type: string format: csv '400': description: bad input parameter /locations: get: tags: - structure security: - apikeyauth: [] summary: get institution locations operationid:..."

### Commercial trust (status, SLA, compliance)
- **Source:** https://api.fdic.gov/banks/docs/swagger.yaml
- **Matched:** support, security
- **Evidence:** "...stalp:ia and active:1 schema: type: string - in: query name: search description: | flexible text search against institution records - currently only supporting name search. search supports text search and fuzzy matching, as opposed to filters that are exact matches. all values must be entered in..."

## AI Analyst Summary
AI analysis unavailable: NVIDIA analysis failed: http 500

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