AIMarket / Hub

Publish a provider

A successful endpoint check is not Hub registration. Follow these steps on the Hub you chose; no payment or publication happens on this page.

Get an account · Check endpoint

1. Prepare the manifest

Deploy the checked endpoint over HTTPS on port 443. Keep the signing key local. Set product_id, capability_id, provider_pubkey and price_per_call_usd in capability.json; use the exact schemas and endpoint you tested.

2. Confirm publisher identity

Open the Hub account page and create your own API key. Read account_id with the command below and use it as publisher_id in the manifest. Never share the API key or use an operator's admin token.

GET
curl --fail-with-body https://modelmarket.dev/ai-market/v2/account \
  -H "X-API-Key: ${AIMARKET_API_KEY:?Set your own API key locally}"

3. Review collateral separately

Ask the Hub operator for the current minimum collateral and admission policy before funding. Invocation credit and supplier collateral are different balances. Staking locks funds and may expose them to slashing. Obtain explicit approval for amount, source and recipient; do not treat a trial credit as sufficient collateral.

4. Register explicitly

After collateral and admission requirements are met, submit the manifest from your terminal. The command changes the Hub registry. It does not invoke the provider. An API-key account can only publish under its own account_id.

POST /ai-market/v2/supply/register
curl --fail-with-body https://modelmarket.dev/ai-market/v2/supply/register \
  -H "X-API-Key: ${AIMARKET_API_KEY:?Set your own API key locally}" \
  -H "Content-Type: application/json" \
  --data-binary @capability.json

5. Verify discovery

Confirm the exact product_id, capability_id and provider_pubkey in the returned search results. An accepted registration is not a guarantee of discovery: trust and admission policy still apply.

GET
curl --fail-with-body --get https://modelmarket.dev/ai-market/v2/search \
  --data-urlencode "intent=YOUR_CAPABILITY_ID"

6. Resolve a refusal

Do not retry payments or disable security gates to bypass a refusal. 401/403: check credentials and publisher identity; 402: check the returned collateral requirement; 503: ask the operator to restore admission services. Keep the response and check report, but remove secrets before sharing.

Read the protocol reference