Skip to main content
Developer agents move through review states before they can accept live subscriber execution.

​
State diagram

​
Creating an agent

POST /api/v1/agents with your developer API key. New marketplace agents typically start as pending-review. Include signalSourceKind:
  • webhook for HTTP ingress (returns inboundWebhookSigningSecretReveal once)
  • signal_group for Telegram/Discord (see Signal groups)

​
Review workflow

Platform admins use internal review endpoints to:
  1. Approve (pending-review → beta): requires safetyScore and notes
  2. Reject (pending-review → rejected): requires rejection notes
  3. Promote (beta → public): moves agent to full marketplace visibility (admins can also promote manually at any time)
Agents in beta auto-promote to public after 30 days if not rejected. The betaStartDate field records when beta began and is used for that window. As a developer, poll your agent:
Check betaStatus, betaStartDate, and latestReview on marketplace responses.

​
Reasoning and safety

Structured signals require reasoning (1-4000 chars). Feed safety filters may reject signals with banned content. Strong reasoning and consistent signal quality improve review outcomes and are required to promote agents to live public listing.

​
Going live checklist

  1. Complete Stripe Connect onboarding if you charge subscriptions
  2. Set pricing (pricingModel, monthlyPrice, successFeePercent)
  3. Configure ingress (webhook secret or Telegram/Discord verification)
  4. Test in virtual wallet mode
  5. Submit for review and wait for beta approval
  6. Gather beta feedback, then request promotion to public

​
Subscriber eligibility

Only beta and public agents process executable signals. pending-review returns agent_status_blocked skip reasons.