A free tool by Track · no account
Will an agent get through your signup?
Reads your public pages and names the steps an agent cannot complete. Track is what you use after the fixes.
Score reads your public pages first, names the steps an agent cannot complete, and writes one prompt per fix. Where only a test can prove a step, it says so. No account, no install, no readiness score.
Run it from your terminal
Works on any public product. The check reads only public pages; the prompts it writes are for your coding agent, so nothing is submitted without you.
npx agent-led-growth check yourproduct.comnpx agent-led-growth check resend.comReal output, 2026-10-22alg check · resend.com Read 21 public pages. GET only, nothing submitted. Not yet. Your pages don't show how an agent signs up, gets a key or pays. Your public pages document 3 of 7 steps. No step has been tested yet: a test runs a real agent. 3 need a fix. 1 needs a test run. passed Discover The site is open to agents and has an index from your files written for them (/llms.txt with 58 links). passed Understand Prices are written in the page text, so an from page text agent can read them, though it has to interpret prose to compare plans. failed Sign up The pages read document no way for an agent from page text to sign up. A person may have to create the account; only a real agent run can confirm. failed Access The docs describe API keys, bearer tokens from your files and OAuth, but the pages read do not show how an agent gets one. passed Use 83 API operations in a machine-readable API from your files spec. failed Pay Paid plans are published. The pages read from page text document no way for an agent to buy one, so a person may have to check out. needs a test run Manage Changing a plan or a limit can only be needs a test run proven by a test run. 3 fixes one prompt each, for your coding agent 01 Sign up Let an agent sign up and a person claim it later 02 Access Document how an agent authenticates 03 Pay Let an agent buy a plan without a browser checkout
alg check · resend.com Read 21 public pages. GET only, nothing submitted. Not yet. Your pages don't show how an agent signs up, gets a key or pays. Your public pages document 3 of 7 steps. No step has been tested yet: a test runs a real agent. 3 need a fix. 1 needs a test run. passed Discover The site is open to agents and has an index written for them (/llms.txt with 58 links). from your files passed Understand Prices are written in the page text, so an agent can read them, though it has to interpret prose to compare plans. from page text failed Sign up The pages read document no way for an agent to sign up. A person may have to create the account; only a real agent run can confirm. from page text failed Access The docs describe API keys, bearer tokens and OAuth, but the pages read do not show how an agent gets one. from your files passed Use 83 API operations in a machine-readable API spec. from your files failed Pay Paid plans are published. The pages read document no way for an agent to buy one, so a person may have to check out. from page text needs a test run Manage Changing a plan or a limit can only be proven by a test run. needs a test run 3 fixes one prompt each, for your coding agent 01 Sign up Let an agent sign up and a person claim it later 02 Access Document how an agent authenticates 03 Pay Let an agent buy a plan without a browser checkout
alg check · resend.com Read 21 public pages. GET only, nothing submitted. Not yet. Your pages don't show how an agent signs up, gets a key or pays. Your public pages document 3 of 7 steps. No step has been tested yet: a test runs a real agent. 3 need a fix. 1 needs a test run. passed Discover The site is open to agents and has an index written for them (/llms.txt with 58 links). from your files passed Understand Prices are written in the page text, so an agent can read them, though it has to interpret prose to compare plans. from page text failed Sign up The pages read document no way for an agent to sign up. A person may have to create the account; only a real agent run can confirm. from page text failed Access The docs describe API keys, bearer tokens and OAuth, but the pages read do not show how an agent gets one. from your files passed Use 83 API operations in a machine-readable API spec. from your files failed Pay Paid plans are published. The pages read document no way for an agent to buy one, so a person may have to check out. from page text needs a test run Manage Changing a plan or a limit can only be proven by a test run. needs a test run 3 fixes, one prompt each, for your coding agent 01 Sign up: let an agent sign up and a person claim it later 02 Access: document how an agent authenticates 03 Pay: let an agent buy a plan without a browser checkout
Real output, kept verbatim. The fixes are prompts, not a score.
What it looks for
The check follows the path an agent takes, then separates what it can read from what only a test can prove.
- 01Discover
Can an agent find you? llms.txt, robots.txt, a sitemap and pages written to be read.
- 02Understand
Are the prices, limits and API operations in the page text or a machine-readable spec?
- 03Sign up and get access
Can an agent create an account, get a key and make the first call without a browser?
- 04Pay
Can an agent buy a plan without a person at a checkout? If not, the check says so.
A page that says an agent can sign up is not proof. Score marks those steps as needing a test run, and names exactly what to fix. A JavaScript-only pricing page is reported as not confirmed, not free. A native app with no documented web API has no web Sign up, Access or Use step.
Score finds the block. Track measures what gets through.
Score is the free check. Track is the analytics layer that shows which agents call your API, which paths convert, and which journeys pay. Run the check first; connect Track when you want the live funnel.
Free during the pilot. No card, nothing to buy.