A8. Recipient API
Status: normative. Document version 1.0-draft-1.
This chapter states the recipient API requirements that do not depend on the binding. The REST binding (B4) gives the HTTP routes, request validation, idempotency, conditional reads, errors and rate limits; the MCP binding (B3) carries the same operations to agents.
Public discovery is unauthenticated; every recipient action is authenticated and authorised.
Unknown or foreign proposal IDs return the same proposal_not_found. Contribution retries are identified by authenticated event ID as specified in A14. Always recheck authority before replaying a stored response; a retry after revocation cannot retrieve protected results.
Body-size, rate and authentication failures do not consume read counts. Only committed fresh disclosures consume reads.
Owner management must support reviewing entries/proposals/grants/history, temporal activation, correction, revocation, export/import and deletion with re-authentication for sensitive changes. The earlier /v1/me/* list was illustrative. Private UI routes are outside this recipient interoperability contract; it does not grant recipients management authority.
Checks: TRANSPORT-01, CORE-01, LOG-01, CONTRIB-02.
References to other standards and projects describe intended technical alignment only and do not imply endorsement or partnership.