For agents
An interface for the agent you already use.
The app has a REST API and an MCP server. Both are built and in private testing with the six tools below. They are not open to the public yet.
Access keys and scopes
The workspace owner issues each key and picks its scopes. A key can do nothing its scopes do not list. New workspaces start with approve and publish switched off on every key; the owner can switch them on.
| Scope | What it grants |
|---|---|
| read | See plans, the queue, facts and results. |
| draft | Submit drafts and propose plans. |
| approve | Approve or reject drafts in the queue. |
| publish | Send approved pieces to their channels. |
Planned plugins
Each plugin is packaging over the same interface, so it can do nothing a key could not. Listing dates depend on each directory's own review.
- Claude connector. Add the product from Claude's directory.First release
- Claude Code plugin. Commands for planning, the queue and approvals in a terminal.First release
- ChatGPT app. The same tools in ChatGPT's directory.Next
- Zapier, n8n and Make. Ready-made steps for automation builders.Next
- Connected tools. Our agents use your analytics or CRM, with scopes you grant.Later
Tools
Names may change before release. Drafts and decisions are written to the run ledger with the name of the key that made them. There is no tool for the publish scope yet.
list_productsneeds readLists the products in the key's workspace.
get_factsneeds readReturns a product's fact sheet. Only confirmed facts may be cited.
list_queueneeds readReturns drafts waiting for a decision, with the facts each line cites.
get_resultsneeds readReturns approved pieces with their tracked link clicks.
submit_draftneeds draftSubmits a draft. Refused with reasons if any claim lacks a confirmed fact or a rule is broken.
decide_draftneeds approveApproves or rejects one waiting draft. Approval is refused if its facts are no longer confirmed.