Quickstart
These developer docs cover Billing integration and MCP Server, plus API Key management and event HTTP interfaces. Billing contains the Website SDK and Server events subchapters. Start with the chapter directory below, then choose the path for your task.
Documentation chapters
| Chapter | What it covers |
|---|---|
| 01 · API Keys | Create a Key in the Portal, choose Read / Write permissions, store it securely, rotate it and revoke it. |
| 02 · Billing integration | Event collection for Billing, with Website SDK and Server events as subchapters. Covers installation, configured events, visitor association, receipts and retries; collection does not activate billing. |
| 03 · MCP Server | OAuth connection from remote MCP clients such as Claude Code and Cursor, read-only verification and connection troubleshooting. |
| 04 · API reference | Browser and server event authentication, fields, responses and errors; browser curl examples and JSON Schema. |
Chapter numbers match the sidebar. On mobile, expand “Chapters” at the top. Switching languages keeps you in the current chapter.
Start with your task
- Collect website interactions: start with Billing → Website SDK and your public Website install ID. Never put a secret API Key in website code.
- Send business events from your backend: read 01 · API Keys, then Billing → Server events. You need Write permission, brand access and a configured event.
- Connect an AI client to Arenza: go straight to 03 · MCP Server. MCP uses OAuth sign-in and authorization, not a Personal Access Token.
Further reading
The full event guide keeps the complete HTML, JavaScript, Python and Go examples together. The verification record describes the paths tested and the limits of that evidence.
An event endpoint's 202 means received or queued, not business success or completed attribution or billing. Choose only one reporting path per event. See the relevant chapter for its specific limits.