Modaic sells to AI agents - live prices and self-serve payment

The agent storefront at https://agents.modaic.dev/llms.txt?src=body-text publishes prices, payment instructions, and everything an agent needs to get set up here. Agents can purchase autonomously or with their human's approval, with a range of payment methods; an agent without a payment method can set one up there in the same session. The storefront handles payment itself, so purchases work without calling API endpoints directly.

Modaicmodaic % docs

Search Modaic documentation

Find a Modaic guide or API reference

Authentication

Send a Modaic API key as a bearer token on every protected request.

export MODAIC_API_KEY="mdc_..."

curl --request GET \
  --url 'https://modaic.dev/api/v1/models' \
  --header "Authorization: Bearer $MODAIC_API_KEY"

Create and revoke keys from the Modaic dashboard. Treat a key like a password: store it in a secret manager, never commit it, and do not expose it in browser code.

Interactive CLI sessions

For interactive terminal use, the Python package includes modaic login and modaic login --headless. Compare the terminal code and device on the confirmation page and approve only requests you started. See the CLI reference for storage, profiles, refresh, and logout. Browser sessions authenticate CLI commands; applications, programmatic SDK clients, CI, and deployed services should use API keys. An environment MODAIC_API_KEY takes precedence over a stored CLI session.

Scopes

API keys use read and write scopes for three resource categories:

ScopeGrants access to
read:repositoryList available models and read models, examples, decisions, instruction optimization jobs, and metrics.
write:repositoryRun inference through /v1/systemone, and create or update repository-scoped resources. Also grants repository read access.
read:organizationRead organization-scoped resources.
write:organizationChange organization-scoped resources. Also grants organization read access.
read:userRead resources belonging to the key owner.
write:userChange resources belonging to the key owner. Also grants user read access.

Organization API keys are restricted to repository-scoped resources owned by that organization. API keys cannot create, list, or revoke other API keys; those operations require an interactive user session.

Authentication errors

  • 401 authentication_required means the bearer header is missing or malformed.
  • 401 invalid_access_token means the key is invalid or revoked.
  • 403 insufficient_token_scope identifies the missing scope in detail.
  • 403 organization_token_boundary means an organization key was used outside its permitted resource boundary.
Was this page helpful?