How can we help?
Search our knowledge base or browse common questions below.
No. We implement a Google Translate v2-compatible endpoint shape for easy migration. This means you can switch from Google Translate to Langbly API with minimal code changes, but we are an independent company with our own translation infrastructure.
Language coverage depends on the configured translation model/provider. If you need a specific language pair, contact us and we’ll confirm support.
Quality depends on the configured translation model/provider and your domain. We recommend evaluating with your own content and edge cases.
Billing is based on the number of characters in your input (`q`). Each plan includes a generous character allowance and overages are billed at a flat $4 per 1M characters. Output characters may be included depending on plan/configuration.
Overages beyond your plan's included characters are automatically billed at $4 per 1M characters. You'll never lose access. We just bill the extra usage at the end of your billing cycle.
Contact support and we’ll help with plan changes.
Yes. Enterprise plans are tailored with custom volumes, limits, and support. Use the contact form and we’ll get back to you with options.
We don’t publish plan-based rate limits in the API yet. Hard limits today are per-request: up to 50 `q` items and 10,000 input characters total. Requests have timeouts (default ~20s total request budget).
Yes! You can send multiple text strings in a single request using the "q" parameter as an array. This is more efficient than making separate requests for each string and counts as a single API call.
When caching is enabled, translation results are cached for up to 7 days by default for identical inputs (source/target/format/text). You can use the Idempotency-Key header for safe retries.
All traffic is encrypted in transit (TLS). We don’t persist request bodies in our database. When caching is enabled, translation results may be stored temporarily to speed up repeats. We store aggregated usage metrics for billing and service operations.
API keys are verified via Unkey. For key creation/rotation/revocation, contact support.
Not currently.