heura Seller verification
What heura checks about a seller, and what it cannot check.
Before an offer goes live
- The provider is chosen from a curated list. The address is filled in for you, and a custom endpoint must be HTTPS.
- Heura tests the key against the provider itself, on the server, with one small request per chosen model. A key that does not work cannot be published.
- Only models heura has a list price for, and only that provider's own models, can be listed.
- The discount is 0% to 80%, a wallet can have at most five offers, and publishing is rate limited.
While it is live
- A probe tests each live offer every ten minutes, through the gateway's own channel test.
- Two failed probes in a row pause the offer automatically. The page shows the reason, with fragments of keys and request ids removed.
- A seller who reports far more tokens than the request could have used is billed only up to what the gateway can bound.
- Earnings are held for 24 hours before they can be withdrawn.
What it cannot check
| Question | Answer |
|---|---|
| Are the weights the ones claimed? | Not verified. A seller could answer a premium model name with a cheaper model |
| Is the answer good? | Not measured |
| Does the seller keep prompts? | Heura cannot see it. Prompts pass through a third-party seller's account |
Do not send secrets or sensitive data through a seller you do not trust. Treat model replies as untrusted text.
Reporting a problem
Include the model you asked for, the time with time zone, and what looked wrong. Do not include API keys.