outsend

Settings

Your whole outsend account, in one place.

Connect an AI

Some outsend features run on an AI. Just provide a personal API key from the provider of choice — billing happens at cost with that provider, no middleman and no markup.

The provider's OpenAI-compatible endpoint, e.g. https://api.example.com/v1.

Create a key:

● connected ○ never tested

All outsend AI features use this model. Without an explicit pick, the default model is (). List auto-detected from the provider key.

Loading model list…
● saved
No key yet? Get one in 5 min
  1. Go to console.anthropic.com and create an account (free)
  2. Section Billing: add credit (the minimum is $5, which lasts a very long time during alpha)
  3. Section API Keys: click "Create Key", copy the key that starts with sk-ant-
  4. Come back here, paste it into the field below, click "Save & test"
Indicative cost: Generating a message or a summary typically costs less than 1 cent. With $5 of credit, hundreds to thousands of operations run before a top-up is needed.

AI spending caps

These are YOUR limits: AI pauses as soon as a call would exceed them.

Today
This month
$
adjustable up to
$
adjustable up to
$
adjustable up to
✓ Saved

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.

Current effective threshold:

This threshold is set by outsend. Need more for a specific scrape? Reach us from the support inbox.

Security — where the key lives

  • 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 exists nowhere 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 forgets 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
If localStorage leaks (XSS, hostile extension, machine access): the encrypted blob is useless to the attacker without the outsend server secret. Revocation stays possible in 30 sec on the provider console as a precaution.

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 — hence the need to keep the server healthy.

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 — never to account management or other keys.

Just want to plug in a tool? Go to Integrations: we generate the key and fill in the snippet.
Key created — copy it now.
It will never be shown again: we only store a fingerprint.

No keys yet.
Usage: send the key in the Authorization: Bearer osk_… header, or X-API-Key. Details and examples: outsend.xyz/docs/api/auth

Support inbox

Your conversations with the outsend team. Every report or suggestion keeps its own thread: read it back and reply here.

Password

Change the password directly here, no need to go through email. Requires the current password. All other active sessions will be logged out after the change.

My data

The account owns own the data collected with outsend (scrapes, enrichments, monitoring). Full export is available at any time, or permanent account deletion (along with all related data).

⬇ Export all my data (ZIP)

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 beforehand, export the data first.