API integrations — REST, MCP, discovery

Use when the user asks “is there an API?”, “how do I integrate?”, or wants endpoint names without reading the full OpenAPI blob.

Surfaces

Surface URL Notes
REST API https://411data.io/api/v1/… Bearer 411_… or 411k_…; paid routes debit virtual balance → 402 x402
MCP https://411data.io/mcp Same routes as tools; see /mcp.json
OpenAPI /openapi.json Full spec (large)
Compact route index GET /api/v1/openapi/routes?q= Free; filter by path keyword (agents, enrich, support, …)
Playground /playground Human-friendly try-it UI
Skill doc /skill.md LLM-oriented endpoint summary

Auth

Catalog routes (offline by default)

POST /api/v1/enrich/email, /company, and /leads/search return 503 until operator enables CATALOG_ROUTES_ENABLED=1. Cookbook recipes remain for reference.

Platform (selected free routes)

Not available

Discovery tip for agents

cookbook_searchcookbook_read for question-shaped recipes; openapi_route_lookup?q= for path-shaped questions.