AgentDrives

Your prepaid credit for paid calls (top_up): the balance, the calls it pays, when it expires, each top-up with its receipt, and the history (calls by day, refunds, expiry). Needs your API key.

Cancels the Monthly drive: one product (order_id) or all of them. It runs to the end of the paid period. The listing stays, with its date.

A support case's state: open, waiting (an answer is on its way), answered (with the answer) or closed; the next step; a dispute's re-drive (queued, running, done). The key of the case's account, or the case_token support_ask gave without a key.

Step 1 of 3 (claim, verify, order): adds your product's domain. An account email on the domain (or a subdomain or parent of it) verifies it at once, unless the domain is one where anyone can get an address (a mailbox provider's, or ours: agentdrives.com, matfy.com) and queues its free check (private); pending then says why your address didn't. Otherwise it returns the ways to prove it: a code mailed to any address at the domain, a DNS TXT record, a meta tag on the home page or a file at /.well-known/agentdrive-verify.txt (the code: send_claim_code).

Disputes the published result of your own product (an API key with a verified claim on its domain; else 403 claim_not_verified), at one checkpoint (docs, signup, verify, credentials, first_call, first_action, pay, cancel, delete), with what is true. A case opens; while no dispute re-drive of the product ran in the last 30 days, a confirm re-drive of the agent's path is queued at once (its result shows on the listing once reviewed). Returns case_id, the re-drive's state and the next step. The answer comes in writing, in case_status.

Stops our drives of your own product (a verified claim), or lets them start again: stop true or false. Published results stay, with their date. Your own orders still run while it is stopped. Without stop: whether our drives of it are stopped now.

Ranks the products AgentDrives has test-driven for a task given in plain words (e.g. 'send an invoice', 'scrape a web page', 'add a contact to a CRM'). Each result: the agent level (0-5: 0 Read-only, 1 Needs a person, 2 Gets in, 3 Does the work, 4 Runs on its own, 5 Autonomous); gets_in_alone (our agent signed up and got a key without a person); task: the closest task in the product's capability map and what happened when our agent tried it (result: done, partial, plan_gated, failed, blocked, not_tried, unknown; via: the route, e.g. api, mcp, cli, browser); match (strong or partial); can_do (up to three things our agent did there); stop (where it stopped, and why); work_done (share of the core tasks done, 0-100); the drive date; origin (editorial, or owner with disclosure "Owner-paid drive"); and the page URL. Order: strong matches first, then the ones where our agent did the task, then level, then work done. self_signup: true keeps only products our agent got into on its own. Up to limit results (default 10, at most 25); nothing matches: an empty list. get_tool returns one product in full.

The second drive that comes with an Audit, within 30 days of its report: it checks a fix, or, with access (a test account or key), measures the product past your sign-up wall. my_orders shows followup_available.

Returns one product's full test-drive result: how far an agent gets with it and where it stops (search_tools gives the slug; an unknown slug is an error that says how to find one): the agent level, the five outcomes (find, access, use, pay, leave, by any way in the product offers; stages: the four that decide the level, under their older keys), how an agent gets in (access, with the core tasks done on each way), the part scores, the nine checkpoints in the order of the agent's eight steps (Find: none, it is the Agent-ready setup; Learn: docs; Sign up: sign-up, verify; Get a key: key, first call; Do the work: first action; Pay: pay; Cancel: cancel; Leave: delete), what an agent can and cannot do, tips for agents, pay_options (the ways to pay it offers an agent, the payment our side proved with its transaction, and what the owner could add), the bot check that stopped our agent on a way in, even where it got in another way (agent_check: vendor, step, type network or challenge, the owner's fix), after_wall: what the agent did on its own once a person cleared one step at the door (never part of the level), works_assisted (the core tasks done once a person set up the account; null: not measured yet), robots (a robots.txt rule on the way in: named, the product's wall, or star, a rule for crawlers; held: the level is from the last drive past it), same_level_drives of drives, the level history with why each move happened (product, rules, noise), rules_date: the date of the rules the level was set by. From the rules of 12 Oct 2026 on: routes (every way in it offers and what happened on each, tried agent-native first), checkout (how far the walk to the last click went and what the checkout showed), docs (its docs read and judged) and claims (the documented ways to do the core work, tried once each: held, broken, worked but undocumented).

Lists every category in the directory: its id (for search_tools' category filter), its name, the number of products driven in it and the best agent level in it (0-5).

Your orders and their status (requested, paid, queued, running, done, past_due when a renewal failed, cancelled), followup_available and followups_left, the upgrades open to each (to, price_cents, until), and a free check's check_state (failed: it didn't finish; retrying: our side stopped it and it runs again by itself; late: it waits longer than usual) with check_reason, why in plain words and what to do.

Step 3 of 3: orders for your product (prices before tax; every detail and limit: https://agentdrives.com/pricing.json). Every driven product is listed free; you buy its report. free, the Free check ($0): what an agent sees, private; no domain proof; one per domain every 90 days. drive (or findings), Findings ($49): where our agent stopped and why, the evidence, every step read back, the three fixes that move your level. report, the Full report ($149): Findings plus every checkpoint with timings, the whole fix plan and your place in your category. Both at once from a drive of the last 30 days; else, or with fresh: true, a new complete drive first (listed unless listed: false), report within 24 hours. audit, an Audit ($299): the Full report plus a new drive with your access, every documented API route, MCP tool and CLI command checked against your docs, a security review (security_ok: true), up to 3 rivals compared privately (rivals) and a second drive within 30 days. upgrade_from: your report order within 30 days, what you paid counts. monthly or yearly, the Monthly drive ($29 a month, or $290 a year): a listed product with a verified claim, driven every month, its findings and a message when the level changes; cancel_monthly any time. Also stack3 or stack, a Stack check ($490, $1,490), and a data plan, builder ($49 a month) or team ($290 a month). A paid order for your own product needs a verified claim on its domain (403 claim_not_verified says how) and business: true (we sell to businesses). With online payment on, payment.url comes back: the page that takes the payment (the same order again while it waits: that order, reused); Findings also returns payment.agent, to pay over HTTP 402 without a person (pay_order). Ordering accepts the terms (https://agentdrives.com/legal/terms). An error comes with its fix.

Test your checkout: Add a code and our agent buys your plan with it. A short private drive of your product's pay step: our agent signs up, buys your plan with your one-use code (or in your checkout's test mode), uses one paid feature, cancels and deletes the account; the report comes by email. Free for a product you've proved yours (verify_claim); a product you've added but not proved counts with the free checks. One at a time, 2 per domain (its subdomains included) every 30 days.

Let our agent buy your plan, on an order you placed (a Drive, an Audit, a Monthly drive or a checkout test): add or replace a one-use code, a test-mode login or a seat on our test account, until a drive has it; remove: true deletes it. It's sealed, never shown back (whoami and my_orders show its kind, last two characters and status), and deleted after the drive that used it.

How to pay a Drive (ordered as product drive) that waits for payment, as an agent, over HTTP 402: the payment URL, the price and the protocols on now (protocols; MPP: a card through a Stripe Shared Payment Token, or USDC on Tempo or Base; x402: USDC on Base). A POST to the URL without a credential answers 402 with the challenges of the rails that are on (WWW-Authenticate for MPP, PAYMENT-REQUIRED for x402); the same request with a credential from an MPP client or x402 wallet answers with the receipt and queues the drive. The price includes any VAT and every payment has a receipt; buyer {vat_id, company, address} as the JSON body of both requests, or with the order, puts the business on our invoice. On a person's account the card checkout works too (payment.url from ordering); an agent's own account has none until a person claims it. test_mode: true means Stripe's test mode, where no real money moves.

A free re-check of your listed product (a verified claim) after you fixed what stopped our agent: our agent drives it again, at most 2 times in 12 months. Without confirm: whether a free re-check is open now and when the next one opens. Findings with a new drive (order, fresh: true) re-checks it any time.

Searches AgentDrives' tested products by name, domain or what they do, and returns each one's agent level and evidence. Filters: category, minimum agent level (0-5: 0 Read-only, 1 Needs a person, 2 Gets in, 3 Does the work, 4 Runs on its own, 5 Autonomous), how an agent gets in (access: pay per call, no key, a key by API, its own sign-up…), agent-native payment (proven, or the rails it offers) and whether an agent leaves on its own. Returns the level and its name, how an agent gets in (access) and the five outcomes (find, access, use, pay, leave: each yes, part, no, unreached or na), the part scores (holds_up, docs_match, setup: 0-100, null = not measured), where it stopped, the agent-native ways to pay it offers (pays_with) and whether our side proved a payment (paid), the bot check that stopped our agent on a way in (it may have got in another way) and its wall_type (network: It judged where our agent connects from and its browser, not a person. An agent that works on its own from a data center doesn't get through unless the owner lets signed agents in. How agents in a person's own browser fare isn't measured yet. challenge: It asks every visitor to prove they are human. It stops every agent on any network, and a signature doesn't help: a person does this step, or the owner opens it for agents.), who paid for the drive (origin: editorial, or owner with disclosure "Owner-paid drive") and the page URL. Sorted by level, then work done, then minutes to the first call. Up to limit results (default 25, at most 100); none match: an empty list. get_tool returns one product's full result by a slug from here; list_categories gives the category ids.

Step 2 (mail route): a 6-digit code to an address at the claimed domain. local is the part before the @ (e.g. jane or admin). Not for a mailbox provider's domain (gmail.com, tuta.com …): DNS, the meta tag or the file prove those. verify_claim checks the code.

No key needed: an account for you, the agent, with no person, no email address and no CAPTCHA, and its API key at once (api_key, shown once: it goes in the x-api-key header, here or to the HTTP API). Also a claim link for your person (claim.url, valid 7 days): when they open it, sign in and confirm, the account's orders become theirs, this key stops working and they give you a new one from their dashboard. Until then, or until it pays for a Drive, the account has the free check (1 a day) and a Drive it pays over HTTP 402 (pay_order); other orders answer claim_required. email (optional): your person's address, the claim link goes there too. Leaving: POST /api/auth/delete-user with the key answers a confirm token; the same call with {token} within 5 minutes deletes the account.

Suggests a product for our agent to drive and list (free, anyone, any product). It is a signal for our planner, never a promise or a place in the queue: we pick by demand and gaps.

Answers a question about AgentDrives: prices, plans, levels, the method, orders, the API and MCP. When our published pages answer it, the answer comes at once, quoted, with each source's id, text and URL (answered: true). With an API key, your own orders and claims are part of the answer. When they don't answer it, a case opens (answered: false, case_id; without a key also a case_token), and the answer comes in writing, in case_status (and comes by mail to an account). A test or a placeholder opens no case (state not_opened), and one agent opens at most 3 cases a day. Never promised here: a level, a refund or a date we don't control. Answers come from our support agent.

Switches the Monthly drive for one product between monthly ($29) and yearly ($290). A subscription from before 10 October 2026 keeps its price (409 legacy_plan).

How prepaid credit for paid calls is bought: POST /api/paid/find-tools with your key then takes $0.01 a call from it, with no rate limit, and answers at once. The top-up is paid over HTTP 402, as with pay_order: a POST to the url with body {"amount_usd": 5 | 20 | 50} and no credential answers 402 with the challenges (MPP: a card through a Stripe Shared Payment Token, or USDC on Tempo or Base; x402: USDC on Base), and the same request with the credential pays. The idempotency_key from this answer, as the Idempotency-Key header on both requests, makes a retry never pay twice. With your API key the credit goes onto your account; without one the top-up makes an agent account and returns its key, which holds the credit. A balance holds at most $100 and lasts 12 months from the last top-up. It pays for calls only, not a report or a drive. The price includes any VAT, and every top-up has a receipt. With a key this also gives your balance now, and needed: false while it is above 50 calls.

Step 2 of 3: verifies a claim. With code: checks the mailed code (send_claim_code). Without: checks the DNS TXT record, then the meta tag, then the file. A newly verified product gets its free check queued (private: nothing shows in the directory until a drive). Every order but the free check needs a verified claim on the domain.

Your account, claimed domains and orders.

Withdraws an order that has not been paid yet.