Seller portal
Claim your service's domain in the Superstables directory, choose whether to opt in to referrals, and see the sales Superstables referred to you.
Signing in moves no funds, costs no gas and grants no spending allowance.
Seller portal
Payments use test tokens. No real money is charged.
Teammates can edit this account's listing pages. Add an email sign-in in Sign-in and people to invite them.
To do
Get started
Claim a domain, then opt in a service. Add credit if its terms include a fee. Claiming doesn't opt you in to anything.
-
1. Claim a domain
To doProve that you control the web address of a service listed in the directory.
Not in the directory yet? Add a service first.
-
2. Opt in a service
To do -
3. Add credit
When neededFees are taken from prepaid credit, so you need it only under terms with a fee.
Credit and sales
Credit
USD
Fees are taken from this credit. At zero or below, services under terms with a fee get no new referrals.
Top-ups
To add credit, ask for a top-up with an API key (POST /api/v1/seller/top-ups with an amount in dollars), then pay its pay URL with a compatible x402 client. It is credited once the payment is final on chain.
| Date (UTC) | Entry | Amount (USD) |
|---|
Referred sales
Payments to your services that carried a Superstables referral, and the fee each one carries.
| Date (UTC) | Service | Chain | Amount | Fee | Transaction |
|---|
Referred sales appear here once a referred payment is confirmed on chain.
Disputes
Dispute a sale your service didn't deliver or refunded. An accepted dispute returns its fee.
Services
Your services
The directory's listings under your domains appear here.
Add a service
List a paid endpoint the directory hasn't found. It must answer with a payment request. It joins the directory unowned until you claim its domain.
Domains
Your domains
A domain appears here once its claim is checked.
Claim a domain
Prove that you control the web address of a service listed in the directory. Claiming doesn't opt you in to anything.
Claim
Prove it with
Each domain has one account. If another seller holds yours, message @superstables on X.
Account
API keys
A key acts for this account only, and stops working when you revoke it.
A key can change the page of every listing your claims cover, and a change is public at once.
New key
Copy it now. It isn't shown again.
Edit listing pages with a key
A listing's public page is https://superstables.com/s/<id>, using the id from GET /api/v1/seller/pages. Read it there to confirm that an edit is live.
Fields: name (80 characters), description (500), and the links website, docs, support and terms. Links start with https://, and support can also be a mailto: address. Send only the fields to change; null clears one.
- GET /api/v1/seller/pages: your listings and their current fields, 100 at a time. Pass next as the after query parameter until next is null; limit accepts 1 to 200
- GET /api/v1/seller/pages/{id}: one listing
- POST /api/v1/seller/pages/{id}: change its fields
- GET /api/v1/seller/pages/{id}/revisions: revisions, newest first, 50 at a time. Pass next as the before query parameter until next is null; limit accepts 1 to 200
To undo a change, read the listing's revisions and POST the earlier revision's whole fields object to the page route, null values included. A revision is the full set of fields as they were, not one field, so this puts all of them back. Every earlier value stays in the revision history.
Take a listing's id from the first route's answer (listing.id) and set it as LISTING. This sets the description:
curl -X POST https://superstables.com/api/v1/seller/pages/$LISTING \
-H "Authorization: Bearer $KEY" \
-H "Content-Type: application/json" \
-d '{"description":"Research reports, paid per request."}'
Fields that don't fit answer 422 and nothing is saved. Each issue names its field. A listing your claims don't cover answers 404.
{"error":{"code":"invalid_fields","issues":[
{"path":"/description","code":"too_long","message":"description must be at most 500 characters"}]}}