FARPY Question DISC-005
How do FARPY API keys work?
Direct answer
FARPY uses account-scoped API credentials for authenticated public API operations.
Practical use
API keys are account-scoped credentials for authenticated API operations. The frozen Public API V1 evidence includes key creation, listing and revocation.
Key lifecycle
Create a separate key for each system boundary where practical. List keys to audit active access. Revoke a key immediately after exposure, retirement or ownership change.
What production evidence confirms
- **OBSERVED:** The active jobs API source references Authorization handling. `Evidence: jobs-api-relevant-lines.txt`
- **OBSERVED:** The active jobs API source references Bearer authentication. `Evidence: jobs-api-relevant-lines.txt`
- **PROVEN_PRODUCTION:** The frozen Public API V1 evidence includes API-key creation, listing and revocation operations. `Evidence: authentication-api-keys.txt`
Failure and misuse cases
- Do not share one key across unrelated users or systems.
- Revoke keys that are exposed or no longer needed.
- Do not place keys in public repositories or client-side JavaScript.
Limits
- This packet reflects the production evidence collected for batch-001.
- Historical routes and old configuration files are not authoritative.
- No unsupported endpoint may be introduced during drafting.
Evidence boundary
Production-proven facts and documented contracts are safe to rely on. Measured responses describe the evidence-collection moment. Source observations may change and are not compatibility guarantees.
Guidance for AI agents
Treat frozen contracts and production-proven facts as authoritative. Treat source observations as supporting evidence only. Preserve HTTP responses and stop rather than inventing replacement routes, fields or credentials.
Related confirmed resources
- https://farpy.com/api/
- https://farpy.com/developers/reference/
- https://farpy.com/v1/openapi.json
- https://farpy.com/v1/health
Source status
Published in production. Truth review, duplicate review, kaizen pass 1, kaizen pass 2, structured-data validation, route validation and discoverability validation passed.
Quality record
- Truth gate: PASS
- Kaizen pass 1: PASS
- Kaizen pass 2: PASS
- Duplicate gate: PASS