Developer overview

Aepto exposes one Platform API, one Connect OAuth stack, and one MCP endpoint. First-party Chrome, WordPress, and Claude clients use the same contracts.

Pieces

Platform API - https://app.aepto.com/api/v1/.... Create keys at app.aepto.com/api-keys (avatar menu → API Keys / MCP). See API overview and Alert webhooks.
Connect - OAuth 2.1-style authorize/token/revoke under https://app.aepto.com/connect/. Used by Chrome, WordPress, Claude MCP, and custom apps. See Connect.
MCP - Streamable HTTP at https://app.aepto.com/mcp (no trailing slash). Install from Claude’s official Connectors Directory, or paste the URL as a custom connector. Tools are named aepto_*. See MCP.

Recommended start

Create an Aepto account and open app.aepto.com/api-keys.
Create a key with the scopes you need (Scopes & keys).
Call a read endpoint from Endpoints, or connect Claude via the official Aepto connector (or paste the MCP URL above).

FAQ

What surfaces does the developer platform include?

Three: Platform API at https://app.aepto.com/api/v1, Connect OAuth under https://app.aepto.com/connect/, and MCP at https://app.aepto.com/mcp. Chrome and WordPress use the same contracts.

Where do I create an API key?

Open app.aepto.com/api-keys (avatar menu → API Keys / MCP). See Authentication.

Should product UI guides live here?

No. End-user product steps are under Docs. This Developers area is for API, Connect, MCP, and integrator notes.

Do Chrome, WordPress, or Claude use pasted API keys?

No. They use Connect (Sign in with Aepto). End-user guides: Chrome, WordPress, Claude.