EveryInfra

List EveryInfra's data platforms and capabilities (106 platforms / 573 capabilities: search, detail, comments, profiles and more). Use it before everyinfra_call_api to get the platform/action, required and optional params, the per-call row limit (max_limit, or page_size for page-based actions) and the price. Pass a platform to also get allowed values, returned fields and what they mean. Free. Data collection only — for AI chat use everyinfra_chat.

Call any EveryInfra data capability and get structured JSON. Priced per platform tier USD 0.56/1K–USD 5.56/1K; failed calls and empty results leave no final charge (anything reserved is restored). Most actions return up to `limit` rows in one call, billed once; multi-target arrays (urls, targets, usernames, tickers) are billed per element, and actions with rows_per_unit per block of rows asked for. Page-based actions (page_size in the catalog) return one page per call, of a fixed size unless page_size_varies (then a short page is not the end); for more, pass the response's top-level next_page_token (some actions repeat it on each row) as page_token — each page is one call. Check platform/action, required params and max_limit or page_size with everyinfra_list_capabilities first. For slow tasks or large limits pass mode=async: you get a job_id at once; read the result with everyinfra_get_job (free).

Read a job submitted with everyinfra_call_api(mode=async). Free; it does not count against the per-minute limit. While status is submitting / running / finalizing, check again later; succeeded: the rows are in results (paged actions also return next_page_token); failed: see error.reason and error.charged; submit_unknown: the submission is still being confirmed — do not resubmit, follow next_action. Only jobs submitted with the same API key are visible.

EveryInfra's OpenAI-compatible text completions with multi-turn history and any input content or format. Free for accounts that have topped up (nothing is deducted); accounts that have not get ai_topup_required. Rate-limited per account by cumulative top-ups (under $100: 50 requests/minute, $100 or more: 500, $500 or more: 5,000, all keys combined); current models: GET /api/v1/models. Good for cleaning collected data: summaries, translation, sentiment labels, topic classification and structured extraction. messages may total up to 45,000 characters; beyond that you get input_too_large — split long documents into several calls.

List the 52 CAPTCHA and bot-challenge types EveryInfra solves. **Call it before everyinfra_solve_captcha** to get three things: the type name, the required/optional params, and **the shape of the solution** (token / cookie / text / number / fields / points / boxes / tokens / indices — a string to submit, coordinates to click yourself, or grid cells to click: each is used differently). Free.

Solve a CAPTCHA or bot challenge and get a ready-to-use solution. USD 0.000139/call–0.004583/call, **charged per successful solve (castle: per token, × count); failed or empty attempts leave no final charge (anything reserved is restored)**. Use it when a target site is blocked by Turnstile / reCAPTCHA / hCaptcha / a Cloudflare challenge page / GeeTest and the like. Params differ per type — check them with everyinfra_list_captcha_types first.

Search and retrieve sources. 17 tools, chosen with `tool`: crawl: Crawl several pages of a site and return their text; say in plain language which pages you want. crosscheck: Run one question through several retrieval chains with different mechanisms, rank sources by how many mechanisms found them, and fetch the original text of the top tier. It answers how far a claim can be trusted, not just what was found. deep: Deep search with text excerpts; full=true also returns the full text. forum: Real people's discussions — an evidence source independent of official docs (when docs say 'supported' and forums describe where it breaks, trust the specific scenario). harvest: Structured site extraction (long-running: tens of seconds to minutes); use it only when crawl cannot get the data. lens: Reverse image search: give an image URL, find pages that use it (the opposite direction of media). map: List a site's page structure — URLs only, no text, fast. media: Find images and videos by keyword. news: News search. places: Places and businesses search. read: Fetch the text of a given URL; it retries other fetch paths automatically when one fails. scholar: Academic literature search; kind=patents switches to patents (publication number, applicant, inventor, filing and publication dates). semantic: Semantic search: describe what you want in one sentence instead of stacking keywords; it finds deep sources whose titles do not contain your words. mode=deep searches deeper (slower, costs more). shopping: Product search and price comparison. similar: Give a URL, find semantically similar pages — something keyword search cannot do. suggest: Search suggestions (autocomplete). web: General web search with site restriction, region, time window and paging. ⚠ To **assert a specific fact** (a version, a price, whether an API exists), use crosscheck: it returns verifiable sources and their agreement tier. Failed or empty searches leave no final charge (anythin

Read the account behind this API key. Free, read-only, any key works. Returns: - balance: total_usd, paid_usd, bonus_usd and bonus_expiring (amount_usd, expires_at) - discount: this month's top-ups (month_topup_usd), the rate in effect and next (rate, threshold_usd, gap_usd = how much more to top up this month for it) - rate_limit: requests_per_minute for all keys combined, key_requests_per_minute, and any rate package with its expires_at - key: this key's id, name, prefix, created_at and expires_at - usage_24h: calls, succeeded, failed and spent_usd in the last 24 hours (this_key: the same for this key) Check the balance before a batch of paid calls; every paid call's billing also carries balance_after_usd.

Takes no parameters.

The account's call records, newest first: request_id, capability, status code, latency, rows returned, whether it was charged, and the amount. Pass request_id (the request_id / X-Request-Id of any call) to look up one call, including its charge's final state (charged, refunded or partly refunded) and any async job it started. failed_only=true lists failures only. Needs the account read permission "requests:read" on this key: keys not limited to product lines have the three read permissions by default; for a key limited to product lines, the account owner turns it on in the console (API Keys → permissions). Free.

Returns the console top-up page link (url) and the current balance (balance_usd). Use it when a call fails with quota_exhausted or ai_topup_required, or when the user asks how to add funds. The account owner pays in the console; this tool creates no order and charges nothing. Any key can use it; accounts whose service provider handles top-ups get topup_unavailable. Free.

Takes no parameters.

Open a ticket with EveryInfra's human support team and get back the ticket number and a link the account owner can open. Use it when calls keep failing or return wrong or missing data, for top-up, charge or refund questions, or to ask for a new platform, capability or field. Put one line in subject; in description say what you called (platform/action or endpoint), when (UTC), the error code and message and what you expected, and pass that call's request_id (and job_id for an async job); write other IDs with a label such as job_id: job_..., because a bare long ID reads as a secret. Never include API keys or passwords. Ask the user first and open it only if they agree. Errors whose fault is request or account need a fixed request or the user, not a ticket; an error's support field carries a ready draft. Any key on the account works and nothing is charged. Retrying the same request returns the same ticket, and the same capability and error code within 24 hours goes into that ticket. Support is online 10:00-24:00 (UTC+8) with a 10-minute average first reply; replies arrive in the ticket and the account owner also gets an email. Check progress and read support's replies with everyinfra_get_ticket (REST: GET /api/v1/support/tickets/{ticket_id}) using the same key, or at the returned link.

Read one support ticket: its status, what happens next, and its latest 100 messages, including support's replies. Use it after everyinfra_create_ticket to check progress, or when the user asks whether support has answered. Pass ticket_id as a plain integer (the number shown as #N, without the #). The key that opened a ticket can always read it; reading the account's other tickets (opened in the console or with other keys) needs the account read permission "support:read" on this key. Any other number returns ticket_not_found. Free; the same result as GET /api/v1/support/tickets/{ticket_id}.