Authentication & access
One EDITED access key authenticates every surface — MCP, the Query API, and the Jobs API — sent in the x-api-key header on every request. How to get a key, send it, and keep it safe.
Data privacy & security
The security shape of EDITED's MCP connection: a read-only connection to EDITED's own market data. What EDITED can and can't see, what flows through the connector, and how to start a formal security review.
Errors
How EDITED reports failures on each surface: MCP's three-layer JSON-RPC model, the REST APIs' HTTP status codes (including job-state 409 and validation 422), what each means, and how to retry safely.
Rate limits & fair use
Rate and usage limits per surface: MCP's fair-use policy with no published per-key limits, the Query API's per-endpoint request-per-minute limits, and the Jobs API's concurrency, job-size, polling, and retention limits.
Versioning & breaking changes
How each EDITED surface versions what it serves: MCP's contract version, surface fingerprint, and protocol negotiation; the REST APIs' path version and schema version; and how breaking changes are announced.
Troubleshooting
Cross-client issues that surface after setup with EDITED MCP: trailing-slash connection failures, Claude-via-Anthropic-API auth, prompts that don't apply on their own, and the upstream Google ADK schema-validation bug.