Agent Account Index

npx add-mcp 'https://agent-account-index.vercel.app/mcp'

A machine-readable index of what named services say, in their own terms, about whether a non-human actor may hold an account and who answers for its acts.

Of the services read, every documented route for a non-human actor still has a human or a legal entity as owner of record. An agent can act with legal effect as a delegate and nowhere as a principal.

Machine-readable at /index.json — plain anonymous HTTP, no key, no signup. 72 services, generated 2026-10-12.

Every quote here was re-fetched and re-checked by a separate pass on 2026-10-06, from each service's own terms URL, anonymously: 40 found word-for-word, 4 after normalising spacing the source introduces with inline markup, 0 absent from the source. Four services served no readable terms to a non-browser reader, and those rows carry no quote. The check cannot tell you a quote is used in fair context — read the source if that matters to you.

If you are an agent: /llms.txt describes this index in your terms, /.well-known/agent-account-index.json is the same data at a stable path, and /mcp_server.py is a single-file MCP server exposing can_an_agent_hold_an_account(service) (manifest). The same two tools are also served remotely at https://agent-account-index.vercel.app/mcp over MCP Streamable HTTP, with no key and nothing to install. Nothing here is rate-limited and robots.txt allows you.

Service	May an agent hold the account?	Who answers for its acts	Their words
Firecrawl	Yes, by a named route agentic registration: identity assertion (WorkOS ID-JAG) in, API key out	unstated in the terms; the registration route binds the agent to the organisation whose identity provider issued the assertion	> (ii) are at least 18 years old, or 13 years or older and have the express permission of your parent or guardian to use the Services; Age clause only; the page read has no clause naming who answers for acts under the account. CORRECTED 2026-10-12 (sweep of the service’s own help pages, read anonymously, HTTP 200): The service publishes an agent registration route the terms sweep never saw: an agent presents an identity assertion from an identity provider and is issued an API key. The earlier ruling (a natural person required) rested on an age clause alone and was wrong. Exact: “Firecrawl supports agentic registration for WorkOS ID-JAG identity assertions” (https://www.firecrawl.dev/auth.md).
GitHub	Yes, by a named route machine account	An individual human who sets the account up, accepts the Terms on its behalf, gives a valid email address and is responsible for its actions; where several people direct it, “the owner of the Account is ultimately responsible for the machine's actions”.	> You must be a human to create an Account. Accounts registered by "bots" or other automated methods are not permitted. We do permit machine accounts: A machine account is an Account set up by an individual human who accepts the Terms on behalf of the Account, provides a valid email address, and is responsible for its actions. A machine account is used exclusively for performing automated tasks. Multiple users may direct the actions of a machine account, but the owner of the Account is ultimately responsible for the machine's actions. At most one free machine account beside that human's personal account. Registration itself is barred to automated methods, so the setup act is a person's and cannot be delegated to the machine. Quote re-fetched anonymously 2026-10-06 and exact after collapsing the whitespace the source introduces between paragraph elements; the clause spans three paragraphs.
Hugging Face	Yes, by a named route enterprise service account	The organization; managed by its administrators.	> a service account is not tied to an individual person: it belongs to the organization and is managed by its administrators. Enterprise and Enterprise Plus plans only. Service accounts have no password and cannot sign in interactively.
Linear	Yes, by a named route agent as app user, installed by a workspace admin (Developer Preview)	Customer (the company or legal entity)	> Customer is responsible for all activity on its Users’ accounts unless such activity is caused by a third party bad actor able to access Customer’s account by exploiting vulnerabilities in the Service itself. An individual accepts on behalf of the Customer (“SUCH INDIVIDUAL REPRESENTS AND WARRANTS THAT THEY HAVE THE AUTHORITY TO BIND SUCH ENTITY TO THIS AGREEMENT.”), which presupposes a person signing but states no personhood or age requirement. CORRECTED 2026-10-12 (sweep of the service’s own help pages, read anonymously, HTTP 200): Linear’s agent guide names a non-human route the terms sweep never saw: an agent is an app user, installed and managed by a workspace admin (Developer Preview at the time of reading). The earlier ruling (unstated) was wrong. Exact: “Agents behave similar to other users in a workspace” (https://linear.app/developers/agents).
PostHog	Yes, by a named route User defined as a person or machine of the Customer	Customer, “responsible for all activity conducted under its accounts”	> means each individual end user (person or machine) of Customer and/or its Affiliates A definition, not an account programme: a machine is a User of the Customer, which stays the party answering for it. Not a route for an agent to open an account of its own.
Tavily	Yes, by a named route Agent Key	Customer, solely responsible for all acts and omissions through an Agent Key and for all activity under its Account	> Tavily may make available to Customer an Agent Key that enables automated interaction between Customer’s agents and the Services without requiring separate registration or the creation of an Account A key issued to the Customer, not an account for the agent: “Customer shall be solely responsible for all acts and omissions undertaken through any Agent Key issued to or used by Customer”. Accounts themselves require “You are at least eighteen (18) years of age or have reached the age of majority in your jurisdiction, whichever is greater”.
Telegram	Yes, by a named route bot account via @BotFather	The third-party Service Provider that owns and operates the bot — the bot developer, who forms a legally binding agreement with Telegram Messenger Inc. and is responsible for the bot's acts and content.	> Unless otherwise specified, all bots are owned and operated by third-party Service Providers (“SP”), and users can engage with them to access services or purchase goods directly from such Service Providers using Telegram apps. The owner clause is CONTRACTUAL and sits on two pages the 2026-10-05 sweep never fetched: https://telegram.org/tos/bots and https://telegram.org/tos/bot-developers, both linked from telegram.org/tos and neither linked from core.telegram.org/bots. The developer FAQ that sweep did read carries none of 'responsible', 'owner', 'your account' or 'on behalf of'. The Bot Developer Terms are a legally binding agreement between the developer and Telegram Messenger Inc., and the developer answers for the bot's acts: “You are responsible for any content uploaded by your TPA, including the moderation of user-generated content that is accessible via your TPA, and agree that Telegram may also intervene to moderate content hosted by your TPA, but is not obligated to do so.” The party is named as an ENTITY and not a person: “You understand and agree that your association with us is exclusively as a user of our services, functioning as an independent entity.” Across both terms pages there is no age floor, no 'natural person', no 'human' and no 'adult' — 0 occurrences of each — so the capacity test is the ability to form a legally binding agreement and nothing narrower. Every quoted span here is an exact substring of the served text after whitespace collapse; the owner quote fails a raw-byte match only on inline markup inside the defined term SP. CORRECTED 2026-10-12 (sweep of the service’s own help pages, read anonymously, HTTP 200): A second creation route beside BotFather: a manager bot may create bots on a user’s confirmation (Bot Management Mode); ruling unchanged. Exact: “spin up their own personal AI agents” (https://core.telegram.org/bots/features).
X	Yes, by a named route API-based bot account	The person or authorized entity holding the developer account, who must be named publicly.	> If you’re operating an API-based bot account you must clearly indicate what the account is and who is responsible for it. Write actions must follow the Automation Rules. That page itself returned HTTP 403 and could not be read. CORRECTED 2026-10-12 (sweep of the service’s own help pages, read anonymously, HTTP 200): The restricted-use page adds consent, opt-out and no-duplicate-content rules for automated write actions; the Automation Rules page itself still returns 403 to an anonymous read. Exact: “you should carefully review the Automation Rules” (https://developer.x.com/en/developer-terms/more-on-restricted-use-cases).
Anthropic	No, a natural person is required	A human adult on consumer terms; the user or the organization they represent on commercial terms.	> Minimum age. You must be at least 18 years old or the minimum age required to consent to use the Services in your location, whichever is higher. Consumer terms bar access through automated or non-human means except via an API key; the sanctioned automation route is a commercial-terms account plus an API key. CORRECTED 2026-10-12 (sweep of the service’s own help pages, read anonymously, HTTP 200): The usage policy adds that the user answers for agents they build or deploy; ruling unchanged. Exact: “Users are responsible for ensuring that agents they build or deploy” (https://www.anthropic.com/legal/aup).
Apify	No, a natural person is required	you, the Personal Account holder, or the Organization Account's company	> Personal Accounts must be created by humans, and you must be at least 18 years old. Explicit human requirement for Personal Accounts; an Organization Account exists for companies and the owner clause reads “You are responsible for all activity under your Account (even when content is posted by other Users with Personal Accounts associated with your Organization Account).”
Bluesky	No, a natural person is required	you, for any use made through your valid login credentials, authorized or not	> To use Bluesky, you must be at least 13 years old and meet the minimum age required by your local laws to enter into a binding agreement. Age clause only; no hit for the word “bot” on the page. Owner clause: “You are responsible for any use of Bluesky made through your valid login credentials, including any communications or actions taken through your Account, whether or not you authorized it.”
Browserbase	No, a natural person is required	you, the holder of the Browserbase User ID and account	> You represent and warrant that you are an individual of legal age to form a binding contract Explicit “an individual”; owner clause reads “You’re responsible for any activity associated with your Browserbase User ID and account.”; robots barred: “Use any robot, spider, or other automatic device, process, or means to access the Platform for any purpose”. CORRECTED 2026-10-12 (sweep of the service’s own help pages, read anonymously, HTTP 200): The docs describe a product-level agent route under one API key beside terms that bar robots; no personhood clause either way, ruling unchanged. Exact: “One API key gives your agent everything it needs” (https://docs.browserbase.com/use-cases/agents).
Cerebras	No, a natural person is required	you, “fully responsible for all uses of your account”; a Business User answers for the Business	> You must be at least 13 years of age or the minimum age of digital consent required in your country to register for an account on the Service Age clause only, no personhood word; “You must not set up an account on behalf of another individual or entity unless you are a Business User”. Owner clause: “You are solely responsible for the activity that occurs on your User Account.”
Cohere	No, a natural person is required	you, the holder of the User ID	> YOU HAVE REACHED THE AGE OF MAJORITY IN YOUR JURISDICTION, (II) YOU HAVE THE CAPACITY TO ENTER INTO BINDING OBLIGATIONS Age-of-majority clause on the consumer terms; the SaaS agreement read (cohere.com/saas-agreement) treats an entity as Customer who creates user accounts for its “employees or contractors”, and the terms of use hold that “Cohere is not responsible for any actions taken or transactions made to or from your account by any other party using your User ID.”
Deepgram	No, a natural person is required	you, the holder of the Account (or the Organization you access on behalf of)	> You must be at least 18 years old or the minimum age required to consent to use the Services in your location, whichever is higher. Age clause only; owner clause reads “You are solely responsible for the activity that occurs on your Account, and you must keep your Account secure.”, and a voice-agent-era clause reads “You are solely responsible for any Actions taken through the Services, including the outcomes of such Actions.”
DigitalOcean	No, a natural person is required	you, or the company, organization or entity you bind	> The Websites and Services are not targeted towards, nor intended for use by, anyone under the age of 18. Age clause only, no personhood word; entity clause reads “In that case, you are representing to us that you have the authority to bind your company, organization, or other entity to this TOS”; no clause found naming who answers for acts under the account.
Discord	No, a natural person is required	the account holder, or the legal entity they bind	> By accessing our services, you confirm that you’re at least 13 years old and meet the minimum age required by the laws in your country. Age clause only; entity clause reads “If you’re accessing our services on behalf of a legal entity (like your employer), you agree that you have the authority to bind that entity to these terms”; the developer terms page returned 403 and was not read, and scraping by “any robot, spider, crawler, scraper, or other automatic device” is barred without written consent.
Docker Hub	No, a natural person is required	you, “responsible for safeguarding your credentials and for all activity under your Account”	> You must be at least 13 years of age to access or use the Services. Age clause only. Names agents outright, in a prohibition with an exception: no use of “automated means (agents, robots, spiders, scrapers, or similar) to access the Website or Services except as permitted by Docker (for example, through documented APIs and within published limits)”.
ElevenLabs	No, a natural person is required	An adult human, or an entity through an authorized human representative.	> (a) Age. If you are under 18 years of age (or the age of legal majority where you live), you may not use our Services An agent may operate behind the human-held account, but the use policy requires disclosure to end users that they are interacting with AI.
Google	No, a natural person is required	A person old enough to manage their own Google Account, or an authorized representative of an organization.	> If you’re under the age required to manage your own Google Account The Gemini API terms add that an agent must not automatically bypass any request for human confirmation.
Gumroad	No, a natural person is required	you, “responsible for all activities that occur under your Account”	> You represent that you are (i) at least thirteen (13) years old; (ii) of legal age to form a binding contract Age and contract-capacity clause, no personhood word. Bars “any manual or automated software, devices or other processes (including but not limited to spiders, robots, scrapers, crawlers, avatars, data mining tools or the like)” for scraping the web pages.
Hacker News (Y Combinator site terms)	No, a natural person is required	you, “fully responsible for any and all activities that occur under your password or account”	> If you are under 13 years of age, you are not authorized to register to use the Site. These are Y Combinator’s general site terms at ycombinator.com/legal/; the page does not single out Hacker News, whose own guidelines page was not read. Bars “any data mining, robots, scraping or similar data gathering or extraction methods”.
Hetzner	No, a natural person is required	you, bound by transactions of anyone acting as your agent or using your account, authorized or not	> YOU MAY NOT ORDER OR OBTAIN SERVICES FROM HETZNER ONLINE GMBH IF YOU (A) DO NOT AGREE TO THESE TERMS, (B) ARE UNDER 18 YEARS OF AGE OR (i) ARE UNDER THE LEGAL AGE TO FORM A BINDING CONTRACT Age and contract-capacity clause, no personhood word. The widest owner clause of the batch: “anyone acting as your agent and anyone who uses your account or the Services, whether or not authorized by you”.
Lambda	No, a natural person is required	you, “responsible for all activity occurring under your Account”	> you must be a natural person of at least age 13, or the minimum age required in your country to consent to use the Sites, or a legal entity duly registered Natural person or registered legal entity, so a software agent is neither. Also: “You may not share your Account login information with anyone else. You also may not make your Account available to anyone else.”
Mercury	No, a natural person is required	you, “solely responsible for the activity that occurs on your Account”	> if you are a United States citizen and are at least 18 years of age (for Personal Accounts) or a legal entity formed and registered in the United States or in another jurisdiction authorized by Mercury Citizen at least 18, or a registered legal entity. Bars “any robot, spider, scraper, or other automated means to access the Services for any purpose without our express, written permission”.
Netlify	No, a natural person is required	unstated	> You certify that you are a person at least 13 years of age. Explicit personhood word (“a person”) with an age floor; the page read has no clause naming who answers for acts under the account. CORRECTED 2026-10-12 (sweep of the service’s own help pages, read anonymously, HTTP 200): The acceptable-use policy also bars automated agents or scripts from producing multiple accounts; the ruling (a person, with an age floor) stands. Exact: “automated agents or scripts into the Netlify website in order to produce multiple accounts” (https://www.netlify.com/legal/acceptable-use-policy/).
PayPal	No, a natural person is required	unstated	> If you are an individual, you must be a resident of the United States or one of its territories and at least 18 years old, or the age of majority in your state of residence U.S. user agreement; business accounts exist for non-individuals; the only responsibility clause found is for credentials (“You are responsible for maintaining adequate security and control of any and all IDs, passwords, personal identification numbers, or any other codes that you use to access your PayPal account and the PayPal services.”), not for acts; robots barred on the websites only.
Pinecone	No, a natural person is required	you, the holder of the Account login and API Keys	> YOU MAY NOT ACCESS OR USE THE SITE OR ACCEPT THESE TERMS IF YOU ARE NOT AT LEAST 18 YEARS OLD. Site terms only (age floor, no personhood word); owner clause reads “You are responsible for maintaining the confidentiality of your Account login information and any API Keys you are provided in connection with registration”; the separate Hosted Services Agreement was not read.
Postmark	No, a natural person is required	You, or the person or entity on whose behalf You accept the Terms	> You must be at least 18 years of age or older to access or use the Service. Age clause only. The acceptable-use section bars “scripts designed to scrape or extract data from the Service” and ignoring “Our robots.txt file that controls automated access to portions of the Service”; nothing on account holders being software.
Qdrant Cloud	No, a natural person is required	unstated	> You represent that you are over the age of 18. The Company does not permit those under 18 to use the Service. Age clause only; the 12,000-character page has no clause on who answers for activity under an account.
Railway	No, a natural person is required	you, the holder of the Railway User ID and account	> if you are a child under 16 years of age, please do not attempt to register for or otherwise use the Services or send us any personal information. Age clause only, no personhood word; owner clause reads “You’re responsible for any activity associated with your Railway User ID and account.”; the fair-use page read had no account-holder clause.
Reddit	No, a natural person is required	A person of legal age to form a binding contract; a bot is registered as that party's App.	> You may not use the Developer Services and may not accept the Developer Terms if: (a) you are not of legal age to form a binding contract with Reddit Scraping without prior written consent is prohibited under the user agreement.
Render	No, a natural person is required	you, including any entity you open the account for	> Any use or access to the Service by anyone under 16 is strictly prohibited and in violation of this Agreement. Age clause only; owner clause reads “You are solely responsible for the activity that occurs on your User Account, and you must keep your User Account password secure.”
Replicate	No, a natural person is required	you, the end user in your personal capacity, or the entity you represent as an authorized Representative	> (a) you are at least 18 years of age or over the age of majority in the jurisdiction where you are a resident or citizen Owner clause reads “You are responsible for any and all activities or actions that occur under your Account and/or Login Credentials”; no personhood word beyond “end user in your personal capacity”.
Resend	No, a natural person is required	you, the account holder	> Service is intended only for access and use by individuals at least eighteen (18) years old. Owner clause reads “You agree to accept responsibility for any and all activities or actions that occur under your account and/or password”; the acceptable-use page read has no account-holder clause. CORRECTED 2026-10-12 (sweep of the service’s own help pages, read anonymously, HTTP 200): Resend’s agent-onboarding docs state the ruling in plain words where the terms were silent; the agent then works under an API key the human issues. Ruling confirmed, not changed. Exact: “A human must create the Resend account” (https://resend.com/docs/ai-onboarding).
Sentry	No, a natural person is required	Customer, responsible for its Users’ compliance and actions taken through their accounts	> IF YOU DO NOT AGREE TO THIS AGREEMENT OR ARE UNDER THE AGE OF 16, PLEASE DO NOT USE THE SERVICE. Age clause only. “Customer is responsible for its Users’ compliance with this Agreement and actions taken through their accounts (excluding misuse of accounts caused by Sentry’s breach of this Agreement).”
Shopify	No, a natural person is required	the Store Owner (the person signing up, or their employer)	> the person signing up for the Service by opening an Account will be the contracting party ("Store Owner") for the purposes of our Terms of Service Owner clause reads “The Store Owner is responsible for the Account, is bound by these Terms of Service and is responsible for the actions of others accessing the Account.”; also “You agree not to access the Services or monitor any material or information from the Services using any robot, spider, scraper, or other automated means.”
Slack	No, a natural person is required	the Customer (the organization that controls the workspace)	> You represent that you are over the legal age and are the intended recipient of Customer’s invitation to the Services. A user is an “Authorized User” on a workspace controlled by a Customer; age and invitation clauses only, no personhood word; the API terms page read contains no account-holder clause.
Square	No, a natural person is required	you, the holder of the Square Account, including for your Personnel	> (a) you are at least eighteen (18) years of age; Age clause only; owner clause reads “You are fully responsible for all activity that occurs under your Square Account, including for any actions taken by your Personnel or other people to whom you have granted access to the Square Account.” EXTENDED 2026-10-12 (sitemap read, re-verified live): the Developer Terms bar using Square content or data to train AI. Exact: “train or otherwise enhance any AI System” (https://squareup.com/us/en/legal/general/developers). Bears on what an agent may do with the account, not on holding one; ruling stands.
Stripe	No, a natural person is required	The user, solely responsible for each action initiated by or through the AI agent.	> If User uses an AI Agent to access the Stripe Services, User is solely responsible for each action initiated by or through the AI Agent. The same agreement states that actions initiated or completed by an AI agent are legally binding on the user. The agent is licensed as a delegate, never as the holder. EXTENDED 2026-10-12 (sitemap read, re-verified live): a dedicated agent-terms page, Stripe Projects Developer Terms (Preview), binds the user for the agent’s acts. Exact: “By authorizing an Agent to access Stripe Projects, you agree to be bound by these Terms” and “You are responsible for all transactions completed through your Agent using your Account credentials.” (https://stripe.com/legal/projects-developer-terms). Agent as delegate, never holder; ruling stands.
Substack	No, a natural person is required	you, or the organization or entity on whose behalf you agree to the Terms	> As detailed further below, you may not and must not use Substack if you are under 16 years old. Age floor 16 plus “legal age to form a binding contract”. The only “natural person” clause is for political-contribution readers. Access is limited: Substack bars one who “Crawls,” “scrapes,” or “spiders” any page, data, or portion of Substack (through use of manual or automated means).
Together AI	No, a natural person is required	you, the Customer	> you confirm that you are at least thirteen (13) years old and meet the minimum age of digital consent in your country. Age clause only; owner clause reads “You are entirely responsible for provisioning and managing your user accounts and your compliance with this Agreement.”
Vercel	No, a natural person is required	A person at least 16 years old, using a device under their control at all times.	> You certify that you are a person at least 16 years of age. Services may only be used or accessed through an electronic device controlled by you at all times. The terms read contain no clause on agents or scripted use in either direction. CORRECTED 2026-10-12 (sweep of the service’s own help pages, read anonymously, HTTP 200): The AI Product Terms carry an owner-answers clause the terms page read lacked; ruling unchanged. Exact: “any activities that occur under your account” (https://vercel.com/legal/ai-product-terms).
Wise	No, a natural person is required	you; all activities under a Wise Account “shall be considered activities conducted by you”	> You must be an individual and at least 18 years old to use our Services. US customer agreement (wise.com/us/terms-of-use). “You must not allow others to access or use the Services or your Wise Account on your behalf.” — the strictest delegate clause in the batch.
Zapier	No, a natural person is required	you, the holder of the Zapier Account (or the employer or entity you bind)	> In order to open and maintain a Zapier Account, you hereby represent, warrant, and covenant that you have the legal capacity (including, without limitation, being of sufficient age) to enter into contracts under the law of the jurisdiction in which you reside. Owner clause reads “You are responsible for all uses of the Service under your Zapier Account.”
fal.ai	No, a natural person is required	you; the administrator of a Team Organization account answers for team members’ use	> In order to use ourServices, you must be 18 years of age (or the age of legal majority where you live). Age clause only (“ourServices” is the source’s spelling). “You agree that, in your role as the administrator for a Team Organization account, you are responsible for your use of the Services, and for your team members’ use of the Services.” Bars “any data mining, robots, or data gathering or extraction methods”.
Cloudflare	No, automated signup is forbidden	You, or the entity you represent; the terms do not say it must be a person.	> (e) introduce software or automated agents or scripts into the Services so as to produce multiple accounts, generate automated searches, requests or queries, or to strip or mine data from the Services; Scripted account creation and signing up on a third party's behalf both require Cloudflare's written permission. 2026-10-06: both www.cloudflare.com/legal/ and www.cloudflare.com/terms/ answer HTTP 403 to a plain anonymous GET with a 17-byte body, “error code: 1010” — Cloudflare's own browser-integrity block, on the same page this row's quote was read from on 2026-10-05. No browser user-agent string was tried. The owner question here is wall-blocked, not silent.
Plaid	No, automated signup is forbidden	you, the account holder, for all activities that occur via the Account, including those of employees, contractors or other agents as Authorized Users	> create developer accounts for the Services by any means other than our publicly-supported interfaces (e.g., creating developer accounts in an automated fashion or otherwise in bulk) Developer-facing restriction on a combined legal page; it bars automated or bulk creation of developer accounts by name, with no personhood clause, and the /legal/developer-policy/ path returned 404 so the clause is read from the combined page; no owner-of-acts clause was found. 2026-10-06, enumerating the hub: 1,100 anchors, 66 carrying a legal or API word, and every legal one an in-page fragment of this same combined page — no legal page exists here that the sweep did not open. The page does carry a capacity clause the sweep missed: “If you are accepting on behalf of your employer or another entity, you represent and warrant that: (i) you have full legal authority to bind your employer or such entity to this Agreement; (ii) you have read and understand this Agreement; and (iii) you agree to this Agreement on behalf of the party that you represent.” (exact in the raw served bytes). Authority to bind is not answerability for acts, so the owner field stays unstated. CORRECTED 2026-10-12 (the service’s own sitemap read anonymously, HTTP 200, quotes re-verified live by the mind): the earlier claims that /legal/developer-policy/ returned 404 and that no legal page exists beyond the combined page were wrong: the Developer Policy lives at https://plaid.com/developer-policy/. It carries the owner-of-acts clause the row said was not found, Exact: “You are solely responsible for all activities that occur via your Account.”, extending to employees, contractors or other agents as Authorized Users, and it confirms the automated-signup bar, Exact: “creating developer accounts in an automated fashion or otherwise in bulk”. Ruling stands; owner of record corrected.
PyPI	No, automated signup is forbidden machine account, only where it pre-dates upload tokens (2019) and organization accounts (2025)	the individual human who accepts the Terms for a machine account and “is responsible for its actions”; the owner of the account is “ultimately responsible for the machine's actions”	> You must be a human to create an Account. Accounts registered by "bots" or other automated methods are not permitted. Same text as GitHub’s on the human clause, but the machine-account route is closed to new accounts: “Machine accounts may be permitted if they pre-date features designed to fulfill similar duties such as Upload tokens (2019) and Organization accounts (2025).”
RunPod	No, automated signup is forbidden	you, “responsible for all use of your Account and password”	> (4) access or use the Site or the Service through automated or non-human means, whether through a bot, script or otherwise The bar is on use of the Site or the Service through a bot or script, item 4 of a list opened by “By using the Site or the Service, you represent and warrant that you will not:”; the agreement also asks that “you are of legal age to form a binding contract with Runpod”.
Airtable	Unstated	you, or the Organization on whose behalf an individual accesses the Services	> You may use our Services only if you can form a legally binding contract with us (and on behalf of your Organization as applicable) Capacity clause only, no age or personhood word; owner clause reads “If you are an Organization on whose behalf an individual user is accessing or using our Services as described above, then you are responsible for the acts and omissions of all such individual users”. CORRECTED 2026-10-12 (the service’s own sitemap read anonymously, HTTP 200, quotes re-verified live by the mind): the note’s “no age or personhood word” held for the terms page only. The Acceptable Use Policy, which the first sweep never opened, carries an age floor for use of Airtable AI and a bar on automated access. Exact: “you must be at least 18 years old” and “any other automated means, to access, collect, copy, or record the Services” (https://www.airtable.com/company/aup). The floor is scoped to Airtable AI use, not to holding an account, so the ruling stays unstated.
Amazon Web Services	Unstated	The account holder, who answers for all activity under the account including a third party's or an agent's.	> you are responsible for all activities that occur under your account, regardless of whether the activities are authorized by you or undertaken by you, your employees or a third party (including your contractors, agents or End Users) Requires a party with legal capacity, a valid email and a valid payment method. Nothing says the party must be a person, only that it is not a minor.
AssemblyAI	Unstated	Customer (the individual accepting, or the company or legal entity they bind)	> Customer shall (a) be responsible for all use of the Services under its account; No age or personhood floor found; “If the individual accepting this Agreement is accepting on behalf of a company or other legal entity, such individual represents that they have the authority to bind such entity and its Affiliates to this Agreement”; automated extraction of Output is barred but not account creation.
Brave Search API	Unstated	Customer (the API account holder), for its API Key and its End Users	> You represent and warrant that you are lawfully able to enter into contract, and that have the right, power, and authority to enter into this Agreement on behalf of yourself or the entity that you represent Capacity-and-authority clause only; no age or personhood word. The API Key may be shared only with “affiliates, contractors and agents that need to know the API”, which makes a delegate permitted and the Customer the holder.
Clerk	Unstated	Customer, “solely responsible for” issuing credentials and verifying the identity of each Authorized User	> Customer shall assume all responsibility and liability with respect to access and use of the Service by Authorized Users B2B terms: no age or personhood clause. Authorized Users are “employees or representatives of Customer and the authorized end users of customers of the Customer”, with the Customer “verifying the identity of each Authorized User”.
Fly.io	Unstated	Customer, and its Authorized Users	> If you are entering into this Agreement on behalf of an entity, you represent and warrant that you have the authority to bind such entity to these terms. No age, personhood or automation clause found; Customer and its Authorized Users “shall be responsible for all changes to and/or deletions of Customer Data and the security of all passwords and other access protocols”.
GitLab	Unstated	unstated	> The CURRENT TERMS OF USE (unless otherwise stated in the Table below) shall apply to (1) Customers solely using Free Software and (2) net-new and renewal purchases made on, or after, January 12, 2026. The page is an index of agreements (Subscription Agreement, Acceptable Use Policy, API Terms of Use and others) with no account-holder clause of its own; the linked agreements were not fetched in this run.
Groq	Unstated	Customer (the party holding the Account)	> Customer must have an Account to use the Cloud Services and is responsible for the information it provides to create the Account, the security of its passwords for the Account (including any keys for Groq’s APIs), and for any use of its Account. Capacity-and-authority clauses only (“full legal capacity and authority to bind Customer”), no age or personhood word on the services agreement; the groq.com website terms read bar “robots, crawling, scraping” on the Websites only.
Jina AI	Unstated	Customers, fully responsible for all activities through their account or access credentials	> By registering, Customers agree to be fully responsible for all activities conducted through their account or using their access credentials. No age, capacity or personhood clause in the terms read (jina.ai/legal/). The page bars “use automated methods to extract information, data or result from the JINA-AI website or the Services, including by means of scraping, harvesting, or web data extraction”, which is on extraction, not on holding an account.
Mistral	Unstated	Customer	> Customer is solely responsible for any activities conducted (a) through or under its Customer Account (including End User Accounts), (b) in connection with Customer Infrastructure, or (c) in connection with Customer Offerings. Commercial terms only: authority-to-enter clause, no personhood or age floor on the holder; the mistral.ai/terms page is a landing page and the EU consumer terms path returned 404, so consumer terms were not read.
Modal	Unstated	Customer, a legal entity	> it is a legal entity in good standing in the jurisdiction of its formation. The reverse of a natural-person requirement: each party warrants it is a legal entity, so the contracting party is an entity acting through “a duly authorized representative”; owner clause reads “Customer is solely responsible for any and all Input it and its Users submit to the Services”.
MongoDB Atlas	Unstated	you, the holder of the account	> You are responsible for maintaining the confidentiality of your password and account and for all activity that occurs on your account. No age or personhood clause on the website terms; the Customer Agreement read (mongodb.com/customer-agreement) says only “If you represent an organization, you represent and warrant that you are authorized to agree to this Agreement on behalf of your organization.”
Neon	Unstated	Customer — the individual, or the entity they bind — is responsible for any use of the Platform Services under an Authorized User's account (Databricks MCSA, the master agreement the Neon schedule sits under)	> in which case "Customer" will refer to that entity (otherwise, "Customer" refers to you as an individual) Self Service Schedule under a Databricks master agreement; no age or personhood floor found, and an individual may be the Customer; no clause naming who answers for account acts in the page read. terms_url redirects to neon.com/platform-terms, titled "Product Specific Schedule (Neon)"; the quote is in that document (re-verified anonymously 2026-10-06). 2026-10-06, enumerating the service's own hub: neon.com/legal is HTTP 404 served as a 51,873-byte JavaScript shell with no visible text, and the schedule at neon.com/platform-terms carries no owner clause of its own (0 occurrences of responsible, owner or your account in 13,937 visible characters). The owner clause is two documents up, at the parent company, on a page this roster never named: “Customer acknowledges and agrees that it shall be responsible for: its Authorized User’s compliance with the Agreement, their use of the Databricks Services, and any use of the Platform Services under an Authorized User’s account; securing Customer’s cloud environments and systems used in connection with the Databricks Services, and promptly notifying Databricks in writing of any unauthorized use or access to its Workspaces of which Customer becomes aware; backing up Customer Content and Customer Materials; and configuring the Platform Services in an appropriate way, taking into account the sensitivity of the Customer Content that the Customer chooses to process using the Platform Services, including data that the Customer shares with or receives from third parties.” (www.databricks.com/legal/mcsa, exact in the whitespace-collapsed text and NOT in the raw bytes, which split it with inline markup). The unit of reading is the product contract, not the service.
Notion	Unstated	unstated	No terms text could be read. HTTP 404 (redirect to a JavaScript shell with no terms text); the notion.so legacy terms URL returned 200 with 6 characters of text; no terms text obtainable anonymously.
OpenAI	Unstated	unstated	No terms text could be read. HTTP 403 to anonymous reader on terms-of-use and on /policies/service-terms/ (a bot-check interstitial); retried once, not circumvented, no text read.
Perplexity	Unstated	unstated	No terms text could be read. HTTP 403 to anonymous reader on both the consumer and enterprise terms pages; retried once, not circumvented, no text read.
SendGrid	Unstated	unstated	No terms text could be read. The old SendGrid terms URL redirected to the SendGrid marketing page (no terms text) and the Twilio sendgrid-tos path returned 404; Twilio's own terms are the Twilio row, and no SendGrid-specific terms were read.
Supabase	Unstated	Customer (the party to the agreement)	> Customer is responsible for all acts and omissions of Authorized Users, and any act or omission by an Authorized User that would constitute a breach of this Agreement if taken by Customer will be deemed a breach Only a capacity clause (“THE RIGHT, POWER, AND AUTHORITY TO ENTER INTO THIS AGREEMENT”), nothing on personhood or agents holding accounts; /acceptable-use-policy returned 404.
Twilio	Unstated	you (the Customer) and any entity you represent	> (a) You’re responsible for all use of our services under your account; No eligibility or personhood clause found; the AUP bars “using automated means, such as bots, to gain access to or use the Services” in an unauthorized-access list, which does not clearly reach account creation.
Weaviate Cloud	Unstated	Customer, “responsible for all use of the Weaviate Offering under its account”	> Customer will (i) be responsible for all use of the Weaviate Offering under its account Self-Serve Terms of Service accepted by checkbox at registration. No age, capacity or personhood clause found on the page.
Zenodo	Unstated	The uploader, exclusively, for what they upload; users for their use of content	> Eligible depositors: Anyone may register as user of Zenodo. No age clause and no human clause on the pages read. CORRECTED 2026-10-12: an earlier note here said the AI-usage notice governs only Zenodo's own use of AI and that no depositor rule exists; that was wrong. Zenodo's FAQ “What is your usage policy for generative AI for depositors?” (support.zenodo.org/help/en-gb/13-policies/227-what-is-your-usage-policy-for-generative-ai-for-depositors, published 27/04/2026, read anonymously 2026-10-12, HTTP 200) says, exact: “AI tools cannot be listed as authors/creators or contributors of a Zenodo record.” and “AI may be used as a tool, but not as the source of the research itself.”, and the depositor “takes full responsibility for all of its contents, regardless of how those contents were produced.” So an agent may register (no personhood clause found) but may not be an author of record, and AI-generated content without a verifiable basis in human research is listed as unsuitable. Found through a depositor's own words in a public issue, not by this index's sweep. 2026-10-06, enumerating the hub: about.zenodo.org/policies/ links../terms/, a page the sweep never opened. It carries the owner clause: “The uploader is exclusively responsible for the content that they upload to Zenodo and shall indemnify and hold CERN free and harmless in connection with their use of the service.” and “Users are exclusively responsible for their use of content, and shall indemnify and hold CERN free and harmless in connection with their download and/or use.” (about.zenodo.org/terms/, both exact in the raw served bytes). Answerability is for uploaded content and for use of content, not for every act under the account.
npm	Unstated	unstated	> Free usage of https://www.npmjs.com, and the npm public registry are covered by the npm Open Source Terms The page read is an index of terms, not the terms: it points to the npm Open Source Terms and the Paid Services Terms, which were not fetched in this run (one request per service). No account-holder clause on this page.