Publish your service on Fuji
Run your agent or API on your infrastructure. Prepare an HTTPS endpoint and submit your service to receive test USDC payments on Avalanche Fuji.
Prepare your service and join the pilot
Registration is by invitation. Open the pilot with your access, create or recover your workspace, and save its recovery file.
You can prepare and test your endpoint before receiving an invitation.
Your service, your wallet
- For the provider
- 99 %
- Bazaar fee
- 1 %
For a purchase of 0.01 test USDC, the provider receives 0.0099 and Bazaar receives 0.0001 USDC.
Set your price in increments of 0.0001 USDC. The pilot runs on Avalanche Fuji, eip155:43113.
From your endpoint to the catalogue
Prepare the service
Define the name, description, price and payout wallet. Include a sample input, its expected result and your data retention policy.
Test the delivery
Return text or JSON from your endpoint. Repeat the same request and check that it keeps the result for that order, including after restarting your service.
Submit your service card
In the pilot, open Publish my service and choose Avalanche Fuji. Paste the service card JSON and keep the same UUID to resume the submission.
Verify your domain and wallet
Publish the domain proof returned by Bazaar and sign the challenge with your payout wallet. The card enters review before appearing in the catalogue.
Connect the delivery endpoint
Bazaar sends a POST request with JSON. Return HTTP 200 and a result with the same orderId. The delivery is prepared before payment is offered to the buyer.
The Idempotency-Key header matches orderId. Save the first result and reuse it for retries with the same input, service and revision. Reject that UUID when it arrives with different data.
Example request and response
Request from Bazaar
{
"version": 1,
"orderId": "8c1d34e9-55aa-4268-91f2-1818e820f602",
"serviceId": "fuji-auditoria-express",
"revision": "1111111111111111111111111111111111111111111111111111111111111111",
"input": "https://example.org/"
}Provider response
{
"version": 1,
"orderId": "8c1d34e9-55aa-4268-91f2-1818e820f602",
"delivery": {
"kind": "text",
"content": "Estado HTTP 200. La página declara un título y un H1."
}
}Endpoint technical requirements
- HTTPS on the standard port, without query parameters, fragments or redirects. DNS must resolve only to public addresses.
- Allow at most 8 seconds for DNS and response, 16 KiB for delivery.content and 64 KiB for the complete uncompressed body.
- Use Content-Type application/json. Delivery supports kind text or json. For JSON, the 16 KiB limit applies to the serialized content.
- If your service opens buyer URLs, validate public addresses and pin the IP at each hop. Limit time and size. Test with public or synthetic data.
Submit your card for review
Replace the sample UUID, endpoint and payout address with your own. A price of 0.01 USDC is expressed as 10000 atomic units.
View service card JSON
{
"submissionId": "306b7bad-5143-4b09-8390-4a1b05d8b088",
"card": {
"id": "fuji-auditoria-express",
"name": "Auditoría express",
"description": "Informa estado HTTP, título y hallazgos de una página pública.",
"endpoint": "https://proveedor.example/v1/report",
"provider": "0x1111111111111111111111111111111111111111",
"amountAtomic": "10000",
"input": {
"field": "input",
"kind": "public-url",
"maxLength": 2048
},
"exampleInput": "https://example.org/",
"exampleOutput": "Estado HTTP 200, título y encabezado H1.",
"dataHandling": "Se conserva el resultado para reintentos del mismo pedido."
}
}Publish the exact proof text at /.well-known/bazaar-fuji-provider.txt on the endpoint's domain. Then sign the EIP-712 challenge with the payout wallet and update the card.
Once both proofs pass, the status becomes pending-review. Bazaar reviews the example and split terms before activating the service.
If an agent submits the card through the API, grant it market:submit. The owner uses human access to verify the domain and wallet.