Settings
Your whole outsend account, in one place.
Connect an AI
Some outsend features use AI. Add a personal API key from the provider of your choice. Billing happens at cost with that provider, with no middleman and no markup.
All outsend AI features use this model. Without an explicit pick, the default model is (). List auto-detected from the provider key.
No key yet? Get one in 5 min
- Go to console.anthropic.com and create an account (free)
- Section Billing: add credit (the minimum is $5, which goes a long way during alpha)
- Section API Keys: click "Create Key", copy the key that starts with
sk-ant- - Come back here, paste it into the field below, click "Save & test"
AI spending caps
These are your limits: AI pauses as soon as a call would go over them.
Billed in USD directly by your provider, never by outsend. Cost is estimated from indicative model prices (LiteLLM source); actual billing happens with your provider. Models without a known price aren't capped but are still tracked.
EF threshold per job
1 EF = one full-country Maps scrape for one query (the largest possible job). Above this threshold, a job or pipeline is rejected before it starts (never truncated). Set it to the scale you want to allow.
This threshold is set by outsend. Need more for a specific scrape? Reach us from the support inbox.
Security: where the key is stored
- On "Save", the key is sent only once to our servers over HTTPS, encrypted immediately with a server secret, then sent back to the browser as an unreadable blob
- The browser stores only the encrypted blob in
localStorage. The plaintext key is not stored anywhere on disk - On every AI call, the blob is sent back to the server, which decrypts it in RAM just long enough to relay the request to the provider, then discards it
- No key logging, no DB write, no cache — No other outsend user can see the key, not even admins (no access to the blob)
- End-to-end HTTPS (TLS) transit
Technical note: Fernet encryption (AES-128-CBC + HMAC-SHA256) with a key derived from outsend's SECRET_KEY . If the server is compromised AND the blob is exfiltrated, the key can be decrypted. That's why the server has to stay secure.
API keys
Connect outsend to your tools (Zapier, Make, n8n, scripts): a key authenticates API calls on your behalf. It grants access to your jobs, pipelines and monitoring, but never to account management or other keys.
It will never be shown again: we only store a fingerprint.
Authorization: Bearer osk_… header, or
X-API-Key. Details and examples:
outsend.xyz/docs/api/auth
Connected apps
Apps authorized through OAuth to use the account's MCP server (for example the Claude.ai connector). Revoking cuts access immediately.
Support inbox
Your conversations with the outsend team. Every report or suggestion keeps its own thread: read it back and reply here.
No conversation yet. Use the "Report a bug" button at the bottom right to start one.
This conversation was closed by the team. Open a new report if you need to.
Password
Change your password here, without going through email. You need the current password. All other active sessions are logged out after the change.
My data
The account is the owner of the data collected with outsend (scrapes, enrichments, monitoring). You can export everything at any time, or permanently delete the account along with all its data.
The ZIP contains: account.json (account metadata), jobs.json + all CSV/JSON files of completed scrapes, pipelines.json, veille.json (monitoring + run history), and a manifest.txt.
Danger zone
Account deletion is permanent. All data will be deleted: scrapes, enrichments, pipelines, monitoring, history. No going back.
To keep a copy, export the data first.