Authentication

Every request to the Sybilion API must be authenticated. The method depends on how you're connecting.

Method	Auth type	How?	Credentials
Direct API calls (curl, HTTP)	API key	Authorization: Bearer header	API keys in the Developers Portal
SDK (Python, Go, R, Java)	API key	Env var or client constructor	API keys in the Developers Portal
MCP (Claude, ChatGPT, TradingView)	OAuth	Browser approval flow	Managed by the MCP client

Missing or invalid credentials return 401 Unauthorized.

Get an API key

In the Developers Portal, navigate to API keys and create a new key.

Important: The full secret is shown only once, at creation time. Copy it immediately — it starts with sk_ops_… and cannot be retrieved again. Keys can be revoked at any time from the same page.

Store it in the SYBILION_API_TOKEN environment variable:

export SYBILION_API_TOKEN="sk_ops_..."

Direct HTTP / curl

Pass the key in the Authorization header on every request:

curl -sS \
  -H "Authorization: Bearer $SYBILION_API_TOKEN" \
  https://api.sybilion.dev/api/v1/me

SDKs (Python, Go, R, and Java)

All SDKs pick up SYBILION_API_TOKEN automatically once it's set in your environment.

MCP (Claude, ChatGPT, TradingView Remix)

MCP integrations use OAuth — no API key is needed. The MCP client handles the full auth flow on your behalf, you just need to approve the access in a browser pop-up. See MCP integrations for setup instructions.