Authentication

§Getting your token#

Tokens are issued from your account and are premium-gated — you mint them after subscribing.

1. 1Sign up or sign in, and subscribe via checkout.
2. 2Go to /account/tokens.
3. 3Click “Generate token” and name it for the agent or script.
4. 4Copy it immediately — the full token is shown once and only its SHA-256 hash is stored.

§Using your token#

Include your token in the Authorization header with the Bearer prefix on every request:

Authorization: Bearer ppc_pat_…

The format is ppc_pat_ followed by 43 base64url characters (51 characters in total). Tokens are user-scoped and inherit your tier.

§Example requests#

The header in action — fetching an article’s full Markdown body, a premium-gated call. With a valid premium token you get the full body (access: full); the same request without it returns only a preview. Swap in any article slug:

curl -H "Authorization: Bearer $ORAKLL_TOKEN" \
  "https://orakll.com/article/<slug>.md"

The same Authorization: Bearer header authenticates the hosted MCP and the premium REST surfaces — one token, every transport.

§Security best practices#

• ·Keep your token secret — never commit it to version control or paste it anywhere public.
• ·Use environment variables — store it in ORAKLL_TOKEN rather than hard-coding it.
• ·One token per agent or script — so if one leaks you can revoke just that one without disrupting the others.

export ORAKLL_TOKEN="ppc_pat_…"

§Rotating & revoking#

Manage tokens at /account/tokens: revoke a token to kill it immediately, and generate a replacement.