See each SET product work, step by step.

Look before paying

A GET on the paid route is free. It states the price, the payment methods, what the report contains and the published scoring rubric with its version, so an agent can decide before it is asked to pay.

GET /api/agent/ai-visibility

HTTP/1.1 200 OK
{
  "price": { "amount": "1.00", "currency": "usd", "unit": "check" },
  "charging": "The page is checked before the payment is taken; a check that fails is not charged.",
  "rubricVersion": "2026-10-11",
  "returns": { "checkVersion": "2.0.0", … },
  …
}

Ask without paying: get the price

The agent posts the page address. A private or malformed address is refused with 400 and never asked to pay; otherwise SET answers HTTP 402 Payment Required (the web's status code for "pay, then repeat the request"), listing every way to pay in one response.

POST /api/agent/ai-visibility

HTTP/1.1 402 Payment Required
WWW-Authenticate: Payment id="SIMULATED", realm="simpleeasytransactions.com", method="stripe", intent="charge", request="…"   ($1.00, card or Link)
WWW-Authenticate: Payment id="SIMULATED", realm="simpleeasytransactions.com", method="evm", intent="charge", request="…"      (1 USDC on Base)
PAYMENT-REQUIRED: <base64 x402 v2: scheme "exact", network "eip155:8453", amount "1000000" (1 USDC), payTo 0x5151515151515151515151515151515151515151,
                   extensions: bazaar (how to call this route) and builder-code (SET's Base Builder Code)>
Cache-Control: no-store

Pay with card, Link, USDC or a credit

The agent picks one way to pay and repeats the same request with proof of payment. Choose a method to see the request.

POST /api/agent/ai-visibility
Authorization: Payment <credential carrying spt_SIMULATED_0001>
Idempotency-Key: sim-order-0001

{ "url": "bakery.example.org" }

POST /api/agent/ai-visibility
PAYMENT-SIGNATURE: <base64 x402 v2 payload: EIP-3009 authorization, SIMULATED>
Idempotency-Key: sim-order-0001

{ "url": "bakery.example.org" }

POST /api/agent/ai-visibility
Authorization: Bearer setk_live_SIMULATED_KEY_NOT_REAL
Idempotency-Key: sim-order-0001

{ "url": "bakery.example.org" }

SET checks the page before charging

SET fetches the page, robots.txt, sitemap.xml, llms.txt and llms-full.txt, and tests whether http:// redirects to https://, within 15 seconds. The page is checked before the payment is taken; a check that fails is not charged.

SET takes the payment and delivers with a receipt

What comes back depends on how the agent paid. Choose a method.

HTTP/1.1 200 OK
Content-Type: application/json
Payment-Receipt: <base64 { "status": "success", "reference": "pi_SIMULATED_0001" }>
Cache-Control: no-store

HTTP/1.1 200 OK
Content-Type: application/json
PAYMENT-RESPONSE: <base64 { "success": true, "transaction": "0xSIMULATED000000000000000000000000000000000000000000000000000001", "network": "eip155:8453" }>
Payment-Receipt: <base64 { "status": "success", "reference": "0xSIMULATED000000000000000000000000000000000000000000000000000001" }>
Cache-Control: no-store

HTTP/1.1 200 OK
Content-Type: application/json
SET-Credits-Usage: acu_SIMULATED
Cache-Control: no-store

Read the score and the fix list

This report was produced by SET's real check (version 2.0.0, rubric 2026-10-11) against the synthetic site. It scored 85 of 100. Findings come most severe first, each with what was observed, why it matters and the fix.

Retry safely

If the connection drops, the agent repeats the same request with the same Idempotency-Key (a name the agent picks for this purchase) and gets the stored result without paying again. The stored report is returned exactly as first delivered. The same key with a different body is refused, so a key can never buy two different results.

POST /api/agent/ai-visibility
Idempotency-Key: sim-order-0001

{ "url": "bakery.example.org" }

HTTP/1.1 200 OK
Idempotent-Replayed: true
(the stored result; no second charge)

Same key, different body:
HTTP/1.1 409 Conflict
{ "error": "idempotency_key_conflict" }

Look before paying

A GET on the paid route is free: it states the price, the unit (one assessment), that the body needs the workflow and every capability, and the Terms version, and it says execution is never authorized.

GET /api/agent/readiness

HTTP/1.1 200 OK
{
  "price": { "amount": "1.00", "currency": "usd", "unit": "assessment" },
  "requires": ["JSON body: workflow and all ten capabilities"],
  "executionAuthorized": false,
  …
}

Describe the workflow

The buyer declares the status of all 10 capabilities, from machine discovery to recovery and reconciliation: implemented, partial, missing or unknown, with optional evidence. This synthetic declaration is for an invoice-paying agent still in sandbox. An Idempotency-Key header (a name the agent picks for this purchase) makes retries safe.

Ask without paying: get the price

The declaration is validated before any price is quoted, so a malformed one is refused with 400 and never asked to pay. A valid one is answered with HTTP 402 Payment Required (the web's status code for "pay, then repeat the request") and every way to pay.

POST /api/agent/readiness

HTTP/1.1 402 Payment Required
WWW-Authenticate: Payment id="SIMULATED", realm="simpleeasytransactions.com", method="stripe", intent="charge", request="…"   ($1.00, card or Link)
WWW-Authenticate: Payment id="SIMULATED", realm="simpleeasytransactions.com", method="evm", intent="charge", request="…"      (1 USDC on Base)
PAYMENT-REQUIRED: <base64 x402 v2: scheme "exact", network "eip155:8453", amount "1000000" (1 USDC), payTo 0x5151515151515151515151515151515151515151,
                   extensions: bazaar (how to call this route) and builder-code (SET's Base Builder Code)>
Cache-Control: no-store

Pay with card, Link, USDC or a credit

The agent picks one way to pay and repeats the same request with proof of payment. Choose a method to see the request.

POST /api/agent/readiness
Authorization: Payment <credential carrying spt_SIMULATED_0001>
Idempotency-Key: sim-order-0001

{ "workflow": { … }, "capabilities": { … all 10 … } }

POST /api/agent/readiness
PAYMENT-SIGNATURE: <base64 x402 v2 payload: EIP-3009 authorization, SIMULATED>
Idempotency-Key: sim-order-0001

{ "workflow": { … }, "capabilities": { … all 10 … } }

POST /api/agent/readiness
Authorization: Bearer setk_live_SIMULATED_KEY_NOT_REAL
Idempotency-Key: sim-order-0001

{ "workflow": { … }, "capabilities": { … all 10 … } }

SET takes the payment and delivers with a receipt

What comes back depends on how the agent paid. Choose a method.

HTTP/1.1 200 OK
Content-Type: application/json
Payment-Receipt: <base64 { "status": "success", "reference": "pi_SIMULATED_0001" }>
Cache-Control: no-store

HTTP/1.1 200 OK
Content-Type: application/json
PAYMENT-RESPONSE: <base64 { "success": true, "transaction": "0xSIMULATED000000000000000000000000000000000000000000000000000001", "network": "eip155:8453" }>
Payment-Receipt: <base64 { "status": "success", "reference": "0xSIMULATED000000000000000000000000000000000000000000000000000001" }>
Cache-Control: no-store

HTTP/1.1 200 OK
Content-Type: application/json
SET-Credits-Usage: acu_SIMULATED
Cache-Control: no-store

Read the blocking controls, in order

Produced by SET's real ruleset (2026-09-28.1) from the declaration above: disposition "not_ready", with 6 blocking controls in the order to fix them.

Or call it as an MCP tool

The same assessment is a tool on SET's MCP server. An unpaid tools/call answers with JSON-RPC error -32042 (MCP's way of saying payment is required) and the challenge, plus the HTTP endpoint and where to buy prepaid credits. Payment inside MCP is card or Link only; for USDC on Base, call the HTTP endpoint named in alternatives.

POST /api/mcp
{ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "agent_payment_readiness_assessment", "arguments": { … } } }

{ "jsonrpc": "2.0", "id": 1, "error": { "code": -32042, "message": "Payment Required",
  "data": { …card or Link challenge…, "alternatives": { "http": { "url": "https://simpleeasytransactions.com/api/agent/readiness" }, "credits": { "url": "https://simpleeasytransactions.com/api/agent/credits" } } } } }

Retry safely

If the connection drops, the agent repeats the same request with the same Idempotency-Key (a name the agent picks for this purchase) and gets the stored result without paying again. The stored artifact is returned unchanged. The same key with a different body is refused, so a key can never buy two different results.

POST /api/agent/readiness
Idempotency-Key: sim-order-0001

{ "workflow": { … }, "capabilities": { … all 10 … } }

HTTP/1.1 200 OK
Idempotent-Replayed: true
(the stored result; no second charge)

Same key, different body:
HTTP/1.1 409 Conflict
{ "error": "idempotency_key_conflict" }

Sign in with your email

At wallet.simpleeasytransactions.com, or in the wallet frame on simpleeasytransactions.com/wallets. Both open the same wallet with the same email sign-in.

Enter the one-time code

Enter the one-time code. Privy creates your wallets in the same step: Ethereum-compatible (this one is your Base address), Solana and Bitcoin.

Copy your Base address

The wallet lists it under Ethereum, Base, Polygon, Avalanche, with a Copy button. Anyone can send USDC on Base to it.

Add money

Three ways to fund the wallet. Choose one to see what happens.

Cash out to your bank

Open the Cash out tab in your Private Wallet, verify once with Bridge, and link your US bank account. Enter an amount from 5 to 1,000 USDC. Bridge gives you a deposit address for that one cash-out; you approve a single USDC send on Base from your Privy wallet, Bridge converts it to dollars and pays your bank by ACH. The 3% fee is withheld from the payout and shown before you confirm.

Know who holds what

You do. Privy's wallets are non-custodial: keys are protected in secure enclaves and sharded so they are never stored whole, and only you can approve a transaction. Bridge moves the money between your bank and your wallet under its money transmitter licenses. SET never holds your funds or your keys.

Choose a plan and describe your business

Pick a plan, the features you need, where customers will pay (website, customer portal, web application, mobile webview), your business and its people, and confirm each statement in Order Form section 8. Saving your details gives you a private link to resume later.

Review and sign the Order Form

The Order Form shows the plan, fees and terms with its SHA-256 fingerprint, so any later change to the signed copy can be detected. You agree to the Terms of Service, the Privacy Policy and the Order Form, confirm you are at least 18 and authorized to sign, and sign electronically by typing your name.

Verify your business with Stripe

SET's platform opens a Stripe account in your business's name, and Stripe's own form, inside the page, collects and checks your business and banking details; SET never sees your ID numbers or bank details. When Stripe is done, you confirm and the order goes to review.

SET reviews the order

SET reviews every application and emails its decision. When accepted, SET countersigns the Order Form and contacts you to schedule the build and set up the monthly platform subscription. Nothing is billed until SET accepts your order and Stripe shows your account can accept live card payments.

SET builds your checkout

Estimated build window after the written agreement, completed Stripe onboarding, and required access: 10–20 business days. Stripe's verification time is excluded. This is a scheduling estimate, not a guaranteed completion date.

Take payments under your own name

Customers pay in an embedded checkout on your site. Your name is on the payment and the card statement, and each payment settles to your Stripe account. SET's 1% is collected by Stripe from each payment at SET's direction. If you refund a customer, SET returns its 1% on the refunded amount.

Sign in with your email

Enter the one-time code and Privy creates your business wallet. Only you can approve a send from it.

Start on Free; upgrade to pay more people

The plan sets how many people you can pay each month; every plan keeps the same batch rules and charges no SET fee per payout. You can pay up to your plan's number of people in a calendar month. Upgrade from Payouts in your wallet, which opens Stripe Checkout.

Add USDC and a little ETH

Send USDC on Base you already hold (no SET fee), buy it with a card through Stripe, or deposit from your bank to your own account number. Keep a little ETH on Base for network fees. (ETH is Base's own coin, used to pay network fees.) Funding with USDC you already hold carries no SET fee; buying USDC with a card carries Stripe's fees, and a bank deposit to your own account number from Bridge carries SET's 3% fee.

Paste your list

One line per person: their Base address, the amount in USDC and, if you like, a private reference. SET checks every line before anything is recorded. The rules: up to 50 recipients, 1.00 to 2,500.00 USDC each and 10,000.00 USDC per batch.

Approve each send

Approve each send in Privy's confirmation screen.

Each payout is marked paid after 3 confirmations

A confirmation is each new Base block after the one holding your payment. SET marks each line paid after 3 of them.

Download one report

Each batch downloads as a CSV with the line number, your private reference, the recipient address, the amount, the status, the transaction hash and a block explorer link. References stay in your browser and the CSV; SET's server stores only addresses and amounts.

Cash USDC out to your bank through Bridge

Open the Cash out tab in your Private Wallet, verify once with Bridge, and link your US bank account. Enter an amount from 5 to 1,000 USDC. Bridge gives you a deposit address for that one cash-out; you approve a single USDC send on Base from your Privy wallet, Bridge converts it to dollars and pays your bank by ACH. The 3% fee is withheld from the payout and shown before you confirm.

Sign in to SET Wallet

Enter your email and the one-time code. Privy, the wallet provider SET uses, creates your self-custodial wallet; only you can approve a send from it.

Verify with Bridge and link your bank

Bridge checks your identity on its own pages and you link your US bank account. Bridge decides who it can serve.

Get your Cash-Out Address

Choose Base or Solana. Bridge creates a permanent USDC address tied to your bank account, set up as a transfer to yourself, with SET's fee for your plan.

Stay on Pay as you go, or upgrade to Pro

Pay as you go has no subscription: SET's fee is 1.5% of each cash-out, so $1.50 on 100 USDC. Pro is $29 a month and SET's fee drops to 0.5%, so $0.50 on 100 USDC. Bridge withholds SET's fee from each cash-out. Pro costs less overall once you cash out more than $2,900 in a month. Your send also pays a small network fee from the wallet you send from. Start Pro from SET Wallet, or with the Start Pro link on the Cash-Out Address page using the same email you sign in to SET Wallet with, so SET can match the subscription to your wallet. When your plan changes, SET changes the fee on your address automatically. Cancel any time in Stripe's customer portal, opened from SET Wallet; Pro lasts until the end of the period you paid for, then your fee returns to 1.5%.

Send USDC whenever you want dollars

Send at least 2 USDC from a wallet you control. Bridge converts it and pays your bank by ACH, which Bridge processes daily. Bridge's documentation says the address "automatically drains any funds sent to it".

Bridge pays your bank

Bridge pays out by ACH, which it describes as a batch rail where funds are queued and processed daily. SET does not promise an arrival time, and your bank's own posting time applies after Bridge sends the payment.