Adjacent Authenticated REST API

REST discovered

Details

URL: https://api.adjacent.markets/api/v1
Docs: https://docs.adjacent.markets/index.md

Authentication

Adjacent API key + Adjacent API key ?api_key=<credential> discovered

Adjacent API key bearer Get token ↗

Sign in to Adjacent, then open Settings → API keys in the app. Create a key, choose the scopes it should carry, and copy the secret when it is shown — the docs say it is returned only once. Use that ak_... secret either as Authorization: Bearer <key>, as ?api_key=<key> on REST endpoints, or as ?apiKey=<key> on the MCP URL for realtime data.

Adjacent bearer token / Clerk session token + Adjacent bearer token / Clerk session token ?api_key=<credential> discovered

Adjacent bearer token / Clerk session token oauth2 Set up OAuth ↗

Adjacent's authenticated API also accepts a bearer token issued by its Clerk-backed auth system. For interactive access, sign in to the Adjacent app and obtain a bearer/session token from that login flow; the developer docs describe this as a "Clerk session token from the app" and the detected OAuth endpoints are authorize and token with scopes openid, profile, and email. Send the resulting token as Authorization: Bearer <token> or ?api_key=<token> on authenticated REST endpoints. The docs do not describe self-service OAuth client registration for third-party developers, so treat this as app-issued bearer access rather than a documented app-registration flow.