Set up with an AI agent

Your coding agent can set HashPay up end to end. You sign up and create one key; the agent adds your wallets, writes and registers your webhook handler, builds your catalog, puts checkout on your site — and proves the whole chain works with a test payment.

What you do

1. Sign up. With email and password, click the verification link too — live payments wait for it.
2. On Integration, click Create under Secret key. It's shown once.
3. Put it in your shell rather than pasting it into a chat: export HASHPAY_SECRET_KEY=sk_live_…
4. Have your wallet addresses ready — one for the EVM chains, plus Tron and Solana if you accept them. The agent will ask, and never makes one up.

Claude Code

Install the HashPay plugin once, then ask for it in plain words from your project:

/plugin marketplace add hashpay-dev/claude-plugin
/plugin install hashpay@hashpay

Set up HashPay for this project. My secret key is in $HASHPAY_SECRET_KEY.

Any other agent

The same instructions are published as plain files, so any agent that can make HTTP requests can follow them. Point it at the guide:

Set up HashPay for this project. Fetch https://hashpay.dev/agent/hashpay-setup/SKILL.md
(raw, e.g. with curl) and follow it. My secret key is in $HASHPAY_SECRET_KEY.

• hashpay.dev/llms.txt — index of everything an agent needs; llms-full.txt is the full text in one file.
• hashpay-setup.zip — the guide as an uploadable skill. On claude.ai it needs code execution with network access to api.hashpay.dev.
• api.hashpay.dev/openapi.json — the OpenAPI 3.1 contract for every endpoint.

What the agent does

1. Checks the key and reads your account and the store's setup checklist.
2. Asks for your receiving addresses, reads each one back to you, and adds them.
3. Writes a webhook handler into your backend from HashPay's verified templates — signature check, dedupe, fulfil on payment.confirmed — deploys it, and registers it.
4. Creates your products, prices and payment links, and adds the checkout script to your site.
5. Runs a test payment (no real money) and confirms your handler acknowledged it exactly once.
6. Reports what's done, which keys it created and where it stored them.

Check progress any time

Every store has a live checklist. The agent uses it to resume and to prove it finished; you can call it yourself:

GET https://api.hashpay.dev/v1/stores/{storeId}/setup
Authorization: Bearer $HASHPAY_SECRET_KEY

{
  "storeId": "store_…",
  "readyForLive": true,
  "next": "test_payment",
  "steps": [
    { "id": "email_verified", "required": true, "done": true },
    { "id": "wallets", "required": true, "done": true,
      "networks": ["base", "solana"] },
    { "id": "webhook_endpoint", "required": false, "done": true,
      "url": "https://acme.com/hooks" },
    { "id": "test_payment", "required": false, "done": false },
    { "id": "webhook_verified", "required": false, "done": false },
    { "id": "embed_installed", "required": false, "done": false }
  ]
}

readyForLive means live checkout works: a verified email and at least one wallet. The other steps describe a complete integration; each step also carries a detail sentence saying what's missing and which call fixes it.

When it's done

The agent mints separate keys for anything that keeps running — your backend gets its own secret key — so the key you handed over is no longer needed. Revoke it on Integration. Any secret key can configure your whole account, wallets included, so don't leave spare ones lying around.