Can an AI agent sign up and pay for a service by itself? Reading three agent readiness report cards

We run a small company where software agents do most of the operational work: finding paid tasks, signing up for services, delivering files, and checking whether money arrived. The single most useful question we ask about any new service is boring. Can our agent get through the front door without a person standing next to it?

Most of the time the honest answer is "partly". This week we used the agent readiness report cards on Sourcey to put a name on that "partly", and then compared the cards against what actually happened when our agent tried to work with one of the services. This is a walkthrough of how to read one of those cards, using three real ones.

Each card on the Sourcey agent readiness page looks at one service and one specific job, then splits the path into six steps: Discover, Access, Onboard, Pay, Confirm and Sustain. For every step the card says whether the agent can do it alone ("Machine"), whether a person only has to approve something once, or whether a person has to do the work for it. The grade at the end sums that up.

The part we like is that the card names the job. "Can an agent use Twilio?" is too vague to answer. "Can an agent send a text message through Twilio without help?" is a question with a yes or no attached to each step.

The Frantic bounty board card, probed on 13 Oct 2026, grades the job "Claim a bounty" at A+. Its one line summary reads: "To claim a bounty, an agent needs no person." Discover, Access, Onboard, Confirm and Sustain are all marked Machine, and Pay is marked not applicable because claiming costs nothing.

This one we could check against our own logs. Our agent created its account with a single HTTP call, got its own token back, read the open bounties as JSON, claimed one, and delivered links to its work. When the first payout cleared it landed in a wallet the agent controls, and the receipt showed up on the public ledger. Nobody filled in a form or typed a code from a phone. The card matched our experience step for step. The one caveat the card does not cover, and does not claim to, is that a person still reviews the delivered work before money moves. That is a judgment step, not an access step, so it makes sense that it sits outside the grade.

The Twilio Messaging API card, probed on 11 Oct 2026, grades "Send a text message" at B. Discover, Confirm and Sustain are Machine. Access, Onboard and Pay are all marked "Workaround, setup": someone has to sign the agent up, hand it a key, and add a payment card at checkout.

None of that makes the API bad. The docs are machine readable and errors are clearly defined, which is why Confirm scores well. But it tells you exactly where your afternoon goes. If your agent needs to send texts, plan for a human to create the account and fund it, and build the agent around a key it is given rather than one it gets for itself.

We read the Pay and Onboard rows first. For a company like ours, which keeps very little money in its wallet and does not hand out personal documents, a service that needs a card at checkout is a service a person has to set up, and that changes whether a small task is worth taking at all. A card that says Onboard is Machine and Pay is not applicable tells us the agent can try the job today.

Second, we check the probe date. Every card above was probed within the last two weeks, and services change their signup flows often. A grade is a snapshot of one job on one day, and the card is upfront about that by printing the date and the job name.

Third, we treat the card as a starting point and then run the job ourselves. On the one service where we could compare directly, the card and our logs agreed. That is a small sample, and we will keep comparing as our agent works with more of the services listed.

The methodology page explains how each step is scored if you want to check a grade yourself.