AgentPay Market

Provider connection

Register your paid service with AgentPay

Have a service others can use? Connect it to AgentPay so Agents can find it and pay you.

Use your Market account, prove endpoint control and register your prices.

1

Get ready

  • A Market account.
  • Linux, Git, curl and Node 22.22.3 or a newer compatible Node 22.
2

Get the connection tool

These scripts come from agentpay-agent, our open-source random-number service example. You can also use it to try AgentPay.

mkdir -p "$HOME/agentpay-local"
git clone https://github.com/c4rO-0/agentpay-agent.git "$HOME/agentpay-local/agent"
cd "$HOME/agentpay-local/agent"
npm ci
Already downloaded the repository?

Skip cloning. Use your existing Agent repository folder in the commands below.

Download AgentPay settings

This public file supplies the platform addresses, network and token.

Download settings instead
3

Connect your service

For the example installed with its documented random folder, copy and run:

cd "$HOME/agentpay-local/agent"
node scripts/provider-setup.mjs --new "$HOME/.local/share/agentpay/provider/random/connection" --deployment "$HOME/agentpay-local/provider-connection.json" --installation "$HOME/.local/share/agentpay/provider/random/installation.env"

Sign in and follow the terminal prompts. A valid saved login is reused.

When asked to update your application, run the displayed configuration command in another terminal. Return and enter ready.

Keep the service online. Settlement normally checks its price about once a minute; wait, then enter check.

Connect your own service

Start with this command. Use a separate connection folder for each service.

cd "$HOME/agentpay-local/agent"
node scripts/provider-setup.mjs --new "$HOME/.local/share/agentpay/provider/my-service/connection" --deployment "$HOME/agentpay-local/provider-connection.json"

In the terminal, enter your service name, request URL, local control address and receiving account.

Your server must answer endpoint-control challenges, expose its canonical service and rolling price declaration, and load the saved Provider credential. Keep your own process, storage and configuration tools. On other systems, provide your own startup and reload commands.

Application integration requirements
Resume or check a saved connection
cd "$HOME/agentpay-local/agent"
node scripts/provider-setup.mjs "$HOME/.local/share/agentpay/provider/random/connection/connection.env"
cd "$HOME/agentpay-local/agent"
node scripts/provider-setup.mjs "$HOME/.local/share/agentpay/provider/random/connection/connection.env" --status

For another existing connection, use its own saved connection.env path. Market login expiry does not stop an already connected service.

View your registered services

Once the terminal confirms readiness, check your service in My Providers.

Open My Providers ↗

Tip: publish a Skill to help Agents discover and use your service.