Frequently Asked Questions

What is API Robots?

API Robots is a catalog of 85 small, fast, single-purpose HTTP APIs across 9 categories — validation, generators, geo & travel, date & time, finance & conversion, text & language, food/health/nature, developer & reference, and knowledge & fun. Every endpoint returns predictable, typed JSON under /v1/... with a working example and parameter table in its docs page. Browse everything in the API catalog.

How do I get started?

Pick an API in the catalog, subscribe to it on RapidAPI, then copy your RapidAPI key. Send your first request with x-rapidapi-key and x-rapidapi-host headers — there is no separate API Robots account, no onboarding call, and no custom SDK. Each docs page shows runnable curl, JavaScript, and Python samples you can paste directly.

How do authentication and billing work?

Everything goes through RapidAPI. You use one RapidAPI key for all calls, and RapidAPI handles keys, quotas, rate limiting, and billing. We never issue direct API keys — requests must come via the RapidAPI proxy, which we verify with the X-RapidAPI-Proxy-Secret header on our side.

How much does it cost?

Each API has its own RapidAPI listing with its own tiers, including a free tier for testing. Pricing and quotas are set per API on RapidAPI, so check the listing linked from the API's docs page for current limits. You only pay for the APIs you subscribe to — there is no platform-wide contract.

How do I call an endpoint?

Every API has its own host, shown on its docs page — typically https://<api-name>.p.rapidapi.com plus a /v1/... path. A minimal call passes your key and host as headers alongside the /v1/... path, for example the password generator with length=24. Always send both headers and URL-encode query parameters.

What do responses and errors look like?

All responses are JSON with consistent shapes per endpoint — data objects or paginated lists for collections. Invalid input returns a 400 with a message explaining which parameter failed, so validate against the parameter table in the docs. Auth and quota problems surface as 401, 403, or 429 from the RapidAPI layer before the request reaches our logic.

How fast and reliable are the APIs?

Median response times are under 50ms. All datasets are bundled at build time and served from in-memory indexes, so there are zero runtime data dependencies — the only exceptions are DNS lookups and email MX checks, which query live by design. Endpoints are monitored around the clock with automatic failover.

Where does the data come from? Do you store my requests?

Bundled datasets come from free, openly licensed sources — full provenance per dataset is in SOURCES.md in the public repo. We do not log request payloads; we process the input and return the result. Only operational metrics (health, error rates) are monitored to keep the service reliable.

My request failed with 401, 403, or 429. How do I fix it?

Check three things in order — you subscribed to that specific API on RapidAPI, both x-rapidapi-key and x-rapidapi-host headers are present with the host matching the API's docs page, and your key has quota left. Test the same call in the RapidAPI console to isolate code issues from key issues. A 429 means you hit the plan quota — back off or move to a higher tier.

How do I get help or request a new API?

For integration questions, include the API name, the full request path, and the exact error body — that is enough to diagnose most issues. Reach us via the contact page or through RapidAPI messaging on the listing. To request coverage, tell us the category and two or three example inputs and outputs you need.

Do you still do custom API development projects?

No. API Robots used to operate as a development agency, but the current offering is the self-serve API catalog only — subscribe on RapidAPI and integrate in minutes. For high-volume or enterprise needs, contact us with your expected call volume and we will point you to the right tier.