> Production API availability: use /api/v1/help?view=guides and the resource operations catalog before following a recipe. Some localhost capabilities are not deployed yet; an absent operation is unavailable.
What this module owns
First-party event collection and analysis. The public collector and the session-scoped reporting APIs have different trust boundaries.
Separate collector and reporting access
POST /analytics/api/collect is the public tracker receiver. Its request contains site_key and events. The collector validates and queues events; a 204 is not proof that a reporting row has been written. Origin checks, rate limits and privacy behavior live in AntsandCollector.
Dashboard APIs under /analytics/api use their session/group checks. Missing or out-of-scope reporting access deliberately returns 404 in this implementation. Do not send a central agent API key and assume it grants dashboard access. Worker execution and retention need their own operational checks; this documentation pass did not schedule a worker.
Agent access status
No explicit /api/v1 route for this module was found in the route inventory. No supported scoped agent adapter is currently documented. The special interface above must be reviewed separately.
Access boundary
External agents use only the versioned operations documented above and returned by the deployed catalog. Browser actions and internal controllers are not substitutes for missing API operations.
Verification before automation
Read back the owned record after a write. On a dedicated local fixture, test missing input, wrong owner, missing scope and stale revisions where supported. Confirm the request did not change state when rejected. Check the generated projection separately from the source record. Never replay sends, payments or deletion requests merely to test connectivity.
See API validation and remaining gaps for the shared test strategy.
HTTP discovery and safety contract
Read GET /api/v1/help?view=guide&resource=analytics for this module's machine-readable guidance. Discover supported operations through its discovery_url when present. A null discovery_url means no direct resource API is documented; related endpoints, when provided, have their own ownership and scope requirements.
Use GET /api/v1/me with your key to confirm identity and scopes. Only request methods and fields supported by this deployment. The shared transport boundary rejects unsupported methods and malformed JSON on covered routes, but field schemas and revision checks remain resource-specific. Notes and Carousels expose typed save schemas and payload-only validation; other modules must not be assumed to share that contract.
Create, update, replace, patch, delete, send and publish are distinct capabilities. An operation absent from the returned catalog is unavailable, not permission to guess a URL. Read back after writes; after a timeout inspect the result before retrying. Never automatically replay a payment, message, deployment or deletion.