Integration Studio
The Studio is where you see the AI agents working on your account, decide how much of your plan they may use, and connect anymrkt to your other systems. Open it at Integration Studio. Everything in it is also available to agents as MCP tools, so an agent can check its own status and usage.
Agents
Every MCP client that uses one of your tokens appears here on its first call, with the name it reports (Claude Code, Cursor…), the token it used, and its state: connected (seen in the last 5 minutes), idle or disconnected. You can see the card it has claimed, its last call, and how many of today's calls were refused.
- Activity — every tool call, newest first, filterable by agent and outcome. Arguments are shown with secrets masked.
- Disconnect frees the agent's slot immediately; Revoke token stops it for good.
- Goal status — pick a board, sprint or epic and get progress, blocked and stalled cards, who is on what, and an on-track / at-risk verdict. Agents get the same report from
agents_status_report.
Usage and limits
Agent tools are metered in units: reads cost 1, writes 5, publishes and cancellations 10, heavy calls (imagery, context transfer) 20. Limits belong to your account, pooled across every key and agent, and reset on the 1st of each month. Selling is never metered — listings, prices and orders are free on every plan.
Your plan sets the ceiling. In the Studio's Usage tab, a slider per tool sets how much of that ceiling your agents may use — a brake against a runaway agent. To go above your plan, upgrade the plan; limits are never sold per key.
| Units / month | free | plus | pro | team | enterprise |
|---|---|---|---|---|---|
| Kanban | 200 | 1,000 | No cap | No cap | No cap |
| Builder | 100 | 500 | No cap | No cap | No cap |
| Scheduler | 100 | 500 | No cap | No cap | No cap |
| GRAIL | 50 | 200 | No cap | No cap | No cap |
| Studio | 50 | 200 | No cap | No cap | No cap |
| Agents at once | 1 | 2 | 5 | 15 | No cap |
| Live API keys | 1 | 3 | 20 | 60 | No cap |
| Webhook destinations | 1 | 3 | 10 | 20 | No cap |
| Tool calls / minute | 30 | 60 | 120 | 300 | 1,000 |
At 80% and 100% of a limit the Usage bar turns amber, then red, and anymrkt emits usage.threshold_reached and usage.limit_reached — subscribe to them under Event destinations to be told elsewhere.
API keys
A key is for one tool on one board, with read, read-and-write or admin access. It is shown once when created; anymrkt stores only its hash. Keys draw on the same account limits as agents.
Connectors
Connections to Trello, Jira, Dropbox, Google Drive and Calendar, Slack and others, stored per board. Test checks the credential is present and usable. Scheduled two-way sync runs are not built yet.
Webhooks
Inbound endpoints are addresses outside platforms post to. Event destinationsare the other direction: anymrkt sends signed events to your HTTPS endpoint, scoped to one brand, one board, or your account, like Stripe's. Set them up in the console under Event destinations; signatures, retries and the full event list are in Studio webhooks.
MCP tools
agents_list_connected,agents_activity,agents_status_reportstudio_usage_dashboard,studio_get_usage_limits,studio_set_usage_limit,studio_get_settingsstudio_list_api_keys,studio_create_api_key,studio_revoke_api_key,studio_get_key_usagestudio_list_connectors,studio_create_connector,studio_update_connector,studio_test_connector,studio_delete_connectorstudio_list_event_types,studio_create_event_destination,studio_send_test_event,studio_list_event_deliveries,events_list,events_get
See the full tool reference for arguments and permissions.