Obscurify.ai API
Privacy-first AI chat platform API. Access frontier AI models — including uncensored options — with the option of payments we can't link to your account. No…
Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.
Overview
Privacy-first AI chat platform API. Access frontier AI models — including uncensored options — with the option of payments we can't link to your account. No email, username or password.
Private sessions: unlinkable API requests
Requests sent with your API key (sk-obs1_...) are tied to your account. The web chat and Android app avoid that with private sessions (unlinkable inference), and the API can use them too. Run the open-source proxy and point your client at it; your key stays the same:
cargo install unlinkable-inference-cli
export OBSCURIFY_API_KEY=sk-obs1_...
export OBSCURIFY_ACCOUNT_NUMBER=1234567890123456 # optional: any machine can rebuild the wallet
unlinkable-inference serve # http://127.0.0.1:8899- OpenAI clients and curl: base URL
http://127.0.0.1:8899/v1. Anthropic clients and Claude Code:http://127.0.0.1:8899. - The proxy uses your key only to move money from your balance into a wallet of blind-signed vouchers on your machine. Each conversation is paid by its own session, bought with those vouchers, and goes to us with a random session secret (
sk-unl1_...) instead of your key. We can't tie it to your account or to your other conversations. We still see your IP address unless you use Tor or a VPN. - Same prices and the same models as your plan. What you spent is on the proxy's page,
http://127.0.0.1:8899/_unlinkable. Your account's/transactionsdoesn't list private conversations, because the server can't tell they're yours. - Our MCP server does the same with
OBSCURIFY_PRIVATE=1(@obscurify/mcp). - To build it into your own app, use the library: Rust
unlinkable-inference(crates.io) or the browser packageunlinkable-inference(npm). The protocol is in SPEC.md.
Setup for Claude Code, Codex, pi, SDKs and curl, and code for your own app: https://obscurify.ai/tutorials/private_sessions
Getting started
- Create an account —
POST /create_accountwith{"accept_tos": true}. You get a random 16-digit account number. Save it: it is the only way to sign in and can't be shown again. Each network address can create a few accounts per hour and per day (over that: 429 withRetry-After), and accounts that are never funded or used are deleted after 30 days. - Get your API key —
POST /generate_tokenwith{"account_number": "..."}. The key starts withsk-obs1_, is computed from your account and is never stored, so you can always get it again from your number. - Add funds — top up on the account page (crypto or card), or with
POST /top_ups: each payment goes on your balance when it confirms. For a payment we can't link to your account, buy a blind voucher instead (POST /vouchers/orders) and redeem it withPOST /vouchers/redeem. - Make requests — pass
Authorization: Bearer sk-obs1_...on every API call, or send them through the private-sessions proxy (above) so they can't be tied to your account.
Who can use the API
Every account with a positive balance, on any plan (Pay As You Go, Casual or Pro); Casual and Pro can also spend their included usage. New accounts may get $1 of starter credit while this month's promo budget lasts. Requests cost the same per-model prices as the web chat. Paid models have no monthly token limit; free models do (Pay As You Go: 1M tokens). Frontier models (GET /frontier_models) need Casual or Pro and uncensored models (GET /uncensored_models) need Pro; other models return 403. An account with no balance and no plan gets 402.
Switching from a username and password
Username + password sign-in and old stored tokens are deprecated and being retired. Responses to requests made with an old token carry Deprecation: true and an X-Obscurify-Notice header. Sign in once with your password (at /account or POST /login) to receive your account number, then use the number from then on; signing in with it deletes the password.
Authentication
All protected endpoints accept a Bearer token in the Authorization header:
Authorization: Bearer sk-obs1_your-key-hereOpenAI compatibility
POST /v1/chat/completions, POST /v1/responses and GET /v1/models are wire-compatible with the OpenAI API. Point any OpenAI SDK at https://obscurify.ai/v1 and it will work. (Older clients may also call them without the /v1 prefix.) Errors on /v1/* are OpenAI error objects: {"error": {"message", "type", "param", "code"}}.
Anthropic compatibility (Claude Code)
POST /v1/messages speaks the Anthropic Messages API, so Anthropic SDKs and Claude Code can use any model here, uncensored ones included. Send the key as x-api-key or Authorization: Bearer; errors are Anthropic error objects. For Claude Code:
export ANTHROPIC_BASE_URL=https://obscurify.ai
export ANTHROPIC_AUTH_TOKEN=sk-obs1_your-key
export ANTHROPIC_MODEL=deepseek/deepseek-v4.1-flash-uncensored
export…Endpoints 39
authentication
- POSTGet a new account number
/account_number/rotateReplace the account number with a new one and return it. The old number stops working immediately, and so do the old API key and every other browser session.… - POSTCreate anonymous account
/create_accountCreate an account with no email, username or password. The response carries a random 16-digit account number, which is the only way to sign in. It is shown… - POSTCreate user account (deprecated)
/create_userDeprecated. Deprecated: use POST /create_account. Username + password accounts are being retired. Register a new account and automatically sign in with a… - POSTGet API key from account number
/generate_tokenExchange an account number for the account's API key. Keys are derived from the account and never stored, so asking again returns the same key until you… - POSTLog in (browser session)
/loginSign in with your account number and receive an HttpOnly session cookie. Username + password sign-in is deprecated and being retired. It still works for… - POSTLog out (destroy session)
/logoutDestroy the current browser session. The session cookie is cleared and the server-side session record is deleted. Example: curl -X POST… - POSTRevoke current API token
/revoke_tokenImmediately revoke the bearer token used to authenticate this request. After this call the token can no longer be used. Example: curl -X POST… - GETList active API tokens
/tokensReturns all active API tokens for the authenticated user. Tokens are masked — only a prefix and suffix are shown for identification. Example: curl… - POSTGet API key
/tokensReturn the account's API key. It is derived from the account, never stored, and stays the same until rotated with POST /tokens/rotate. Example: curl -X POST… - POSTRotate API key
/tokens/rotateRevoke the account's current API key everywhere and return a new one. Legacy stored tokens are not affected; revoke those with DELETE /tokens/{token_id}.… - DELETERevoke API token by ID
/tokens/:token_idPermanently revoke a specific API token by its UUID. Use GET /tokens to list token IDs. Example: curl -X DELETE…
chat
- POSTCreate chat completion
/v1/chat/completionsSend a conversation to an AI model and receive a completion. Wire-compatible with the OpenAI Chat Completions API: point any OpenAI SDK at… - POSTCreate a message (Anthropic Messages API)
/v1/messagesGenerate a reply with the Anthropic Messages API shape, so Anthropic SDKs and Claude Code can use any model. Same models, plan rules and per-token prices as… - POSTCount the tokens of a message (estimate)
/v1/messages/count_tokensTakes the same body as POST /v1/messages and returns {"input_tokens": n}, an estimate of about four characters per token. Free. - GETPick up a background reply
/v1/replies/:idA streamed chat completion sent with "background": true keeps generating when your connection drops; its id is in the X-Obscurify-Reply response header. This… - POSTStop a background reply
/v1/replies/:id/cancelClosing the connection doesn't stop a background reply; this does. What was written so far stays readable until the reply expires. - POSTCreate a response (Responses API)
/v1/responsesGenerate a reply with the OpenAI Responses API shape. input is a string or an array of input items (messages, images, function call outputs). Same models,…
tee
- GETGet the TEE gateway's attestation report
/v1/tee/attestation?model=string&nonce=stringThe gateway's attestation report, unchanged: its signing keys (attestation.workload_keyset) and an Intel TDX quote whose report data binds those keys to your… - GETGet a TEE reply's signed receipt
/v1/tee/receipts/:id?model=stringThe receipt the enclave gateway signed for an encrypted reply: hashes of the request it received and of the exact bytes it returned, the model host it…
decisions
- POSTAsk a decision model typed questions
/v1/decisionsDecision models answer named, typed questions about the state you send, with calibrated probabilities instead of generated text. Find them in GET /models…
models
- GETList frontier model patterns
/frontier_modelsReturns glob patterns (exact IDs or * wildcards) identifying models that require a paid tier to use. Example: curl https://obscurify.ai/frontier_models - GETList uncensored model patterns
/uncensored_modelsReturns glob patterns (exact IDs or * wildcards) identifying models that require the Pro tier. These models have reduced content filtering. Example: curl… - GETList available AI models
/v1/modelsReturns every model you can call right now, in the OpenAI models-list shape plus each model's per-token prices (USD, everything included) and context window.…
account
- POSTDelete account
/account/deletePermanently delete the signed-in account. The account number, password, email, API key, plan and every browser or app session stop working at once, and the… - GETGet account tier and usage
/account_tierReturns the authenticated user's current subscription tier, monthly fee, billing dates, token usage for the current billing period, and how much of the plan's… - GETList available account tiers
/available_tiersReturns all account tiers with their monthly fees, included usage credit (USD at list prices) and descriptions. This is a public endpoint — no authentication… - POSTChange account tier
/change_tierUpgrade or downgrade the authenticated user's subscription tier. Upgrading to a paid tier charges the first month's fee from the account balance immediately.… - GETGet account balance
/get_user_balanceReturns the authenticated user's current account balance in USD, rounded to two decimal places. Example: curl https://obscurify.ai/get_user_balance \ -H… - GETGet transaction history
/transactionsReturns the authenticated user's transactions, newest first: usage charges, plan fees, deposits and credits. Amounts are signed: positive for credits,… - GETGet spending per day, week or month
/transactions/summaryTotals the authenticated user's transactions per day, week or month in their time zone, newest first. Only periods with activity are listed. Each period's…
payments
- POSTAccept Terms of Service
/accept_tosRecord that the authenticated user has accepted the current Terms of Service. This must be done before the account can be used for paid operations. Example:… - GETGet cryptocurrency exchange rates
/get_ratesReturns current BTC/USD and XMR/USD exchange rates (and their inverses) used for deposit value calculations. Example: curl https://obscurify.ai/get_rates - GETYour recent top-ups
/top_upsTop-ups from the last 7 days, newest first, with what each has credited so far. Open ones are checked with the payment provider first. - POSTTop up your balance
/top_upsStart a payment that goes straight on your balance. Card and Lightning need an amount; BTC, XMR, ETH, USDC and USDT take any amount sent to the returned… - GETVoucher signing keys
/vouchers/keysPublic keys for each voucher amount. Clients blind voucher messages against these keys (RFC 9474, RSABSSA-SHA384-PSS-Deterministic). Every client gets the… - POSTPay for vouchers
/vouchers/ordersStart an anonymous payment. Card and Lightning need an amount; BTC, XMR, ETH, USDC and USDT take any amount sent to the returned address, any number of times.… - GETVoucher order status
/vouchers/orders/:order_idHow much an order has received and how much is left to collect as vouchers. Crypto addresses keep counting payments, including late, partial and repeat ones. - POSTCollect vouchers
/vouchers/orders/:order_id/signSign blinded vouchers against what an order has received. Sending the same blinded vouchers again returns the same signatures without counting them twice, so… - POSTRedeem vouchers
/vouchers/redeemAdd vouchers to the signed-in account's balance. Each voucher can be redeemed once. The server checks the signature but cannot tell which purchase the voucher…
API details
- Base URL
https://obscurify.ai- Authentication
- A bearer token in the Authorization header
An API key in the session cookie - Operations
- 39 operations on 37 pathsPOST 22GET 16DELETE 1
1 marked deprecated - Main resources
- authentication 11payments 9account 7chat 6models 3tee 2decisions 1
- Response formats
application/jsontext/event-stream- Description format
- OpenAPI 3.1.0, API version
1.0.0 - Links
- OpenAPI document · Support
- Listed from
- Obscurify's published OpenAPI description
How to test the Obscurify.ai API in Swastik Codes
- Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
- Fork it into your workspaceChoose a workspace. You get your own copy of the Obscurify.ai API collection, without the publisher's secrets.
- Add your credentialsThis API uses A bearer token in the Authorization header. Add yours in the collection's variables or an environment; the requests already reference it.
- Send a requestPick an endpoint, for example “Get a new account number” (POST /account_number/rotate), and press Send. Check the response, add tests and run the whole collection with the runner.
Frequently asked questions
What is the Obscurify.ai API?
Privacy-first AI chat platform API. Access frontier AI models — including uncensored options — with the option of payments we can't link to your account. No… It is listed under AI & machine learning and has 39 endpoints.
Who publishes the Obscurify.ai API?
It is listed from Obscurify.ai's public API description (an OpenAPI document), not published by Obscurify.ai on Swastik Codes. Anyone who controls obscurify.ai can claim the profile by adding a DNS TXT record.
What is the base URL of the Obscurify.ai API?
Requests go to https://obscurify.ai. Endpoint paths are added to this base URL.
How do I authenticate with the Obscurify.ai API?
It accepts 2 methods: A bearer token in the Authorization header; an API key in the session cookie.
How many endpoints does the Obscurify.ai API have?
39 operations on 37 paths (22 POST, 16 GET, 1 DELETE). The largest groups are authentication, payments, account, chat.
Is forking the Obscurify.ai API free?
Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.