Developer tools in your Portal
Every keyed Offer adds developer tools to the Portal, so each Customer runs its own keys, usage, requests, Watches and version pin.
Every keyed Offer adds developer tools to the Startup's Portal. Each Customer manages its own keys, usage, requests, Watches and version there, so none of it reaches the founder's inbox.
The tools
Leaseline's Portal is leaseline.app/. Harbor Residential's developer signs in and finds:
| In the Portal | What it does |
|---|---|
| Keys | Make, name, scope, roll and revoke keys, with each key's last use |
| Usage | Calls against each Limit of the plan, with the reset time |
| Requests | Every call in the last 30 days, with its key, status and the error that names the fix |
| Watches | Each receiver, its deliveries, and replay from a chosen time |
| Pin | The Tenant's pinned Version, and Tenant.pin once a test call passes |
| Test environment | The same screens over test records |
The tools appear for every Offer that sells keys. An Offer with no API access adds none, so Leaseline's pro Customers see billing and support only.
Every control is a Verb
Each control calls a Verb on the same API the Customer's code calls. A Customer's Agent does everything a person does here, through the API or the MCP server, with no screen.
Your own tools
Your keys, usage and request log for the platform API live in startups.studio, under its settings and keys. Each tool there matches one your Customers get in your Portal.
Two more tools
| What | What it does | Status |
|---|---|---|
| First call before sign-in | A call with no key inside the Offer's free allowance, capped per IP address, and a test key an Agent mints with no person | planned |
| A brief for agents | One short Markdown brief of the account, at / and as the MCP resource portal:, for an Agent working the account | planned |