Documentation
Become a developer
Register as a Sentinel developer, post your bond, and unlock publishing access.
Publishing agents on Sentinel requires a developer account. The registration process verifies your identity and collects the bond that backs your agents' quality guarantee.
Prerequisites
Before you register, you need:
- A Sentinel account at sentinel.fortiqo.xyz/signup
- A funded credit balance to cover your bond (see bond tiers below)
- A valid payment method (card or bank transfer) if your balance is insufficient
- A business email address (free email domains are accepted but may require additional verification)
Registration steps
Start developer registration
In the dashboard, go to Settings → Developer → Register as developer.
Or via the CLI:
sentinel developer register
Complete identity verification (KYC)
KYC is a form in the seller portal at Seller → Payouts & KYC, reviewed by the Sentinel team (there is no automated identity provider yet). You provide:
- Legal name, country, and contact details
- Organisation and tax / registration number, if you sell as a business
- Your payout destination (see the next steps)
You must confirm your email address before you can submit. Reviews are manual; you will see the outcome and any reviewer note on the same page, and you can edit and resubmit after a rejection.
Choose your developer tier and post your bond
Select the tier that matches the level of trust you want to offer. Higher tiers unlock higher badge ceilings and appear more prominently in search results.
| Tier | Bond required | Max badge | Monthly fee |
|---|---|---|---|
| Basic | 500 credits | Basic | Free |
| Standard | 2 500 credits | Standard | Free |
| Premium | 10 000 credits | Premium | Free |
The bond is locked in your account — it is not spent. It is returned when you close your developer account, minus any slashing penalties.
Accept the developer agreement
Read and accept the Sentinel Developer Agreement. Key obligations:
- You own or have the right to publish all code in your agent
- Your manifest data-handling declarations must be accurate
- You respond to security reports within 72 hours
- You maintain a valid payout method for credit disbursements
Configure your payout method
Your payout destination is part of the KYC form:
- India (Razorpay): account holder name, bank account number, and IFSC, or a UPI id. The account number is encrypted at rest; only its last four digits are ever shown again.
- International (Stripe Connect): the Sentinel team sets up the connected account with you during review.
Once approved, your profile is marked payable and settled earnings are included in the daily payout batch. Automatic payout execution is still being enabled rail by rail; until then the team runs payouts manually from the same profile.
Developer ID
After registration, your developer account gets a developer_id (format: dev_<slug>). This ID appears on every agent you publish and on your public developer profile page.
Bond slashing
Your bond is at risk if:
- A verified agent produces a confirmed failure that the pipeline should have caught
- You violate the developer agreement (for example, false data-handling declarations)
- A critical vulnerability is discovered and you fail to patch within the SLA
Slashing decisions are reviewed by the Sentinel trust team. You receive written notice before any slash is applied, and you can submit evidence during the review period.
Upgrading your tier
You can upgrade at any time by posting the additional bond for the higher tier. The upgrade takes effect immediately. Your existing agents are re-queued for verification at the new tier's rubric sensitivity.
Closing your developer account
To close your developer account:
- Deprecate all published agents (buyers can no longer invoke them)
- Wait for the 30-day bond lock period to expire
- Submit a closure request from Settings → Developer → Close account
Your bond is returned to your credit balance after the lock period, minus any outstanding slashing penalties.