- 00
- Features
- Own Provider Keys
Your provider keys, our routing.
Add the keys of your own provider accounts. Tasks run on them with the same API, routing, retry and fallback, and your provider bills you for the solve.
Provider keys
- Free each month, listed value
- $500
- Fee after that
- 2%
- Own keys per organization
- 100
- Modes
- 3
01Mode
One setting decides whether a task may leave your keys.
| Value | In the dashboard | What happens |
|---|---|---|
| first | Own keys first | Your own keys run each task first. If none can, it continues on AnySolver keys at the normal price. |
| only | Own keys only | Only your own keys run tasks. If none can, the task fails with an own-key error at no charge. |
| off | AnySolver keys only | Tasks run on AnySolver keys at the normal price. |
- 01
settings.routing.byokin the requestFor that task only. - 02Own keys on the API keyOr Workspace default, to follow the workspace.
- 03Own keys on the workspaceSet in the workspace settings.
- 04Otherwise
firstThe first one set wins.
02Order
Your keys go first. AnySolver's follow only if you allow it.
- 01Rank as usualRouting mode, provider order, exclusions and a pinned provider apply first.
- 02Your keys move to the frontEach provider you hold a usable key for runs first, in ranked order, on your key.
- 03Workspace keys before organization keysWithin one provider, keys limited to the task’s workspace go first, in random order so load spreads.
- 04Then AnySolver keys, if allowedWith
first, every ranked provider follows on AnySolver keys. Withonly, nothing follows.
- Mode on a new workspace
- first
- Attempts per task, all keys
- 30
03Cost
The fee starts after the allowance. A failure on your key is free.
Your provider bills you for each solve at your rate there. AnySolver's fee counts each task at its listed price.
Example: Multibot lists ReCaptchaV2TokenProxyLess at $0.12 per 1,000 solves, the cheapest quote that the free value, not the task count, limits. The allowance is per organization and UTC month, and ends at whichever limit comes first.
- Free tasks a month, up to
- 5,000,000
- Failed task on your key
- $0.00
- Example: free solves
- 4,166,666
- Example: fee per solve after
- $0.000003
04Limits
Each key has its own thread limit, spend caps and health check.
| Setting | Range |
|---|---|
| Thread limit | 1 to 100,000 at once, or none |
| Spend caps | Up to 5, per any whole number of hours, days or weeks up to 90 days, or in total |
| Connection proxy | Optional, one per key |
| Scope | The whole organization, or chosen workspaces |
| Status | Means |
|---|---|
| Checking | AnySolver is asking the provider about the key |
| Active | The key runs tasks; its provider balance is rechecked on a schedule |
| Rejected | The provider refused the key: invalid, revoked or not allowed from the IP |
| Out of balance | Your provider account holds less than the provider's most expensive task costs |
| Proxy unreachable | The key's connection proxy cannot reach the provider |
| At its cap | The key reached its total spend cap |
05FAQ
Questions about Own Provider Keys.
01
How do I see which key ran a task?
Send settings.statistics: true and each attempt in getTaskResult says whether it ran on your key or on AnySolver keys, and which of your keys. The task details in the dashboard show the same.
02
What happens when my key runs out of provider balance?
The key is marked out of balance and the next of your keys for that provider is tried. With none left, a task in first mode continues on AnySolver keys at the normal price, and a task in only mode fails with BYOK_KEY_NO_BALANCE at no charge.
03
Can the same key also be in Provider Exchange?
No. A provider key belongs to one program at a time, your organization's own keys or Provider Exchange, matched by a fingerprint of the key.
04
How are the keys stored?
Encrypted with envelope AES-256-GCM. The dashboard only ever shows the last characters of a key, and removing a key erases it an hour later.