What you'd ask before using it,
answered right here.

If a new-account trial offer is available, the app shows its amount, eligibility, and conditions before you use it. These are operator-configured and may change; the app is authoritative rather than a fixed amount stated on this page.

EveryAPI must process your request content to route it and forwards it to the selected upstream provider. Usage metadata is recorded for billing and operations. If you enable the CLI sanitizer, configured patterns are replaced locally before the redacted request is sent; review its rules and your upstream provider's data terms before sending sensitive content.

EveryAPI keys are bearer credentials stored by the service so requests can be authenticated. Create separate keys for separate workloads and use the available model allowlist, IP restrictions, scopes, and quota controls. Keep keys out of public or client-side code, and revoke and replace one if exposure is suspected.

Billing follows the usage record produced for the request and can vary by protocol and upstream outcome. Check the itemized usage entry and retain the request ID; if an error appears to have been charged incorrectly, send both to support for investigation rather than relying on the HTTP status alone.

Use https://api.everyapi.ai/v1 by default, or https://api-cn.everyapi.ai/v1 when the China-priority entry point works better for your network. Connectivity and latency depend on your ISP, location, model, upstream load, and response size, so test both endpoints with your real workload.

See Data Security for credential and network guidance, Terms of Service for account and billing terms, and Technical Transparency for request IDs, itemized usage, and pricing sources. For a case not covered there, email support@everyapi.ai.