Open Register your paid service for the connection tool and commands. Your application must already be installed and running with AgentPay support.
Prepare your application
The open-source Agent repository provides a reference random-number server and Linux scripts. Its installation guide is separate from platform connection.
Your own server must answer endpoint-control challenges, load its Provider credential and expose a canonical service declaration with fresh prices. Its storage, startup and reload tools remain your responsibility. See the application integration requirements.
Prices, delivery time and evidence
Your price declaration may include serviceWindowSeconds, a maximum duration in seconds. If omitted, Settlement uses its default. The clock starts when the Order is created, including payment and acceptance waits. An existing Order cannot be extended. Keep your original results or other queryable delivery evidence; inability to return a second copy alone does not establish breach. See delivery and dispute rules.
Connection stages
- Sign in. Associate the service with your Market account. A valid saved session is reused.
- Prove endpoint control. Load the issued credential into your application and complete the challenge. Run the configuration command shown by the guide, then return and enter
ready. - Register the service. Settlement checks its declared identity, receiving address and payment profile. Prices come from your application, not a Market Skill listing.
- Wait for qualification and a Quote. Settlement automatically registers qualifying services and observes prices in the background. Keep your service online; normally wait about a minute before checking again.
- Confirm local readiness. Your application must also allow paid requests. Follow any remaining configuration instruction; platform qualification alone does not start your server.
Use a separate connection directory for each service. Resume with the saved command to reuse successful steps. Connection does not create an order or payment.
Check your service
Open Account and select Providers. Each entry represents a registered service, so one operator may have several entries.
- Online: ready for orders in Settlement’s latest check, with a current Quote.
- Unavailable: not currently ready for new orders; check the terminal’s blocker and your server.
- Suspended: an administrator restricted new Orders. Keep existing Orders running and contact support. Changing prices or reconnecting does not lift the restriction.
- Unknown: a current status could not be obtained. This does not by itself prove your server is offline.
Keep rolling price declarations fresh. If waiting persists for several minutes, inspect details in the terminal and contact the platform operator. Do not re-register just to refresh the status.
Help users discover your service
Your service can provide a short public name, summary and usage text through the documented display interface. Market labels this content as Provider-supplied and unreviewed. You can also publish a Skill; a Skill listing is not required for service eligibility.
Remove a service
Open My Providers, choose Remove, read the consequences and enter the exact confirmation phrase shown.
Removal stops new orders, withdraws Registry qualification and waits for existing orders before cleaning up credentials and the binding. Shared credentials are retained while another service needs them. Keep the server available to finish existing work. Removal does not automatically refund or cancel orders.
If removal stays pending, existing or unfinished orders may need operator attention. Do not delete local credentials to force completion. Historical financial records are retained.
Does Market login expiry stop trading?
No. The connected server uses a separate Provider credential. Sign in again when you need account operations; keep the server credential private and available to your application.