For stores
Know which AI shoppers to trust.
Publish your rules for AI shoppers once, as a signed Store Policy. Every AI order is checked against them, and against the shopper’s own Pass, before PayPal takes a cent.
Demo: PayPal sandbox, test money, fictional demo stores. You are editing a demo store in your own sandbox.
Play the 90-second tourSee it first: the store side, live
Pick your demo store
Ask about thisFour fictional stores. The fifth, a lookalike scam store, can’t sign a policy, so it isn’t here.
How your store treats AI shoppers
Ask about thisPublished policy
Test it with Scout
Run a real check (no money moves) of Scout, the demo AI shopper, against your rules.
Opportunities
Ask about thisRule-based suggestions from your own orders. Each one re-runs your past AI orders against a small rule change and shows what would have happened. Nothing changes until you press Apply.
How AI shoppers are doing at your store
Live numbers from your demo sandbox’s Handshakes.
Test it with ScoutOpen the shopper page
What this means for you: loading…
Outcomes by day
Green: both said yes. Yellow: waited for a person. Red: refused, no money moved.
- Both said yes
- Needs a yes
- Refused
AI shoppers at your store
How is trust worked out?Trust is a 0 to 100 heuristic from each agent’s own history on this server, not a network reputation.
Recent AI orders
Every row has a proof pack: the Pass, your signed policy, the signed receipt and the PayPal sandbox ids.
For developers: verify a Pass in your checkout
For merchants
Check an AI agent's Pass before you take its money.
An AI agent wants to pay you through PayPal. Is it still allowed to? One call, right before you capture, tells you if this amount is inside its owner's limits, or if the owner pressed Stop all a minute ago.
Free · No login · Checks record nothing · Fails closed
- 1AI agent → youSends its order and its Lowtides PassA signed spending permission from the Lowtides server that governs it.
- 2You → PayPalReads the order's real amountFrom the PayPal order, never from what the agent says.
- 3You → LowtidesChecks the pass for that amountSignature offline, revocation and limits online:
POST /v1/pass/verify. - 4You → PayPalCapture, hold or refuseRefused? Void the authorization so the buyer's money is released.
Live checkout simulator
A real check against this Lowtides server with a real pass. Only the PayPal step is simulated, so no money moves on this page.
What your checkout does
- 1Read the passThree base64url parts, EdDSA, type lowtides-pass+jws.
- 2Signature, offlineEd25519 with Web Crypto in your browser, keys from /.well-known.
- 3Revocation and limits, onlinePOST /v1/pass/verify for this amount and merchant.
- 4PayPalCapture, keep holding, or void.
Waiting
Load or paste a pass, then press Check Pass and capture.
This agent's limits, from its pass
Add it to your checkout
Put the check right before your PayPal capture call. Use the amount from the PayPal order, and the Lowtides server you trust, never the URL written inside the pass.
// npm-free ES module: integrations/merchant-check/lowtides-pass-check.js
import { checkPass } from "./lowtides-pass-check.js";
const order = await paypal.getOrder(orderId); // your PayPal client
const v = await checkPass({
pass: req.body.lowtidesPass, // sent by the agent
amount: Number(order.purchase_units[0].amount.value), // from PayPal, not the agent
merchant: "Acme Data", category: "data",
verifyUrl: "https://lowtides.ai/v1/pass/verify", // the server you trust
});
if (v.decision === "capture") await paypal.captureOrder(orderId);
else if (v.decision === "refuse") await paypal.voidAuthorization(authId);
// "hold": keep the order open until the owner approves in Lowtides
console.log(v.label, v.reasons);
# Standard library only: integrations/merchant-check/paypal_capture_guard.py
from paypal_capture_guard import CaptureGuard, PayPalOrders
guard = CaptureGuard(PayPalOrders(CLIENT_ID, SECRET), # sandbox by default
merchant="Acme Data", category="data",
verify_url="https://lowtides.ai/v1/pass/verify")
result = guard.capture(order_id, agent_pass)
# result["action"]: "captured" | "held" | "refused" (refused AUTHORIZE orders are voided)
print(result["action"], result["reasons"])
curl -s -X POST https://lowtides.ai/v1/pass/verify \
-H "Content-Type: application/json" \
-d '{"pass": "PASTE_THE_PASS", "amount": 45.00, "merchant": "Acme Data", "category": "data"}'
# {"valid": true, "revoked": false, "would_allow": "needs_owner_approval",
# "reasons": ["$45.00 is over the $25.00 auto-approve limit."], ...}
# allowed -> capture needs_owner_approval -> hold denied / invalid -> refuse
Public keys for the offline check: /.well-known/lowtides-pass-keys.json. The JS module on this page is the same file: lowtides-pass-check.js.
What one check covers
A PayPal approval proves the buyer said yes once. The pass tells you the agent is still allowed to, right now.
Genuine
Ed25519 signature, checked offline. A changed limit or forged pass is refused.
Not revoked
Stop all, STOP, a loop-guard pause or the owner's Revoke show up at once.
Inside the limits
Per purchase, today's total, approval line, blocked categories and merchants, hours.
Fails closed
Lowtides unreachable? The answer is hold, so nothing is captured on a guess.
Why merchants care: a runaway or hijacked agent turns into refunds, disputes and chargebacks for you. Checking the pass first means you only take money its owner still allows, and you have a signed record of the permission you relied on.
Questions
Why should a merchant check an AI agent's pass?
A PayPal approval only proves the buyer approved the order at that moment. The Lowtides Pass tells you whether the agent is still allowed to spend this amount at your store right now, and whether its owner pressed Stop all. That cuts disputes and chargebacks from runaway or hijacked agents.
When should I check the pass?
Right before you capture the PayPal order or authorization, using the amount from the order itself, not a number the agent tells you.
What if Lowtides is down?
The checker fails closed: the answer is hold, so nothing is captured until the check succeeds.
Does checking a pass cost money or record anything?
No. POST /v1/pass/verify is free, needs no login and records nothing. It runs the same checks a real spend request would and reports what would happen. More on the format: LOWTIDES-PASS.md, or paste a pass into the pass checker.