Skip to main content
Some pages in your Closient dashboard have a Copy for your AI agent button. It copies a capsule: a plain-text work order you paste into Claude, Cursor, or any other AI agent so the agent can do a piece of catalog work for you, such as filling in a product’s nutrition panel or adding products from your website. The agent does the work through Closient’s API or MCP server. You stay in control: you decide what to paste, and you approve the agent’s access in your browser.

What the button does

  1. You click Copy for your AI agent on a supported page.
  2. Closient writes a capsule that describes the current state of that page’s product, brand, or organization, and copies it to your clipboard.
  3. You paste it into your agent.
Click See what your agent will receive under the button to read the exact text before you copy it. The capsule is generated on the server from your real data, so it always matches what is in your account when you click. The button only appears on pages where an agent can complete the work end to end.

Where the button appears

Anatomy of a capsule

Every capsule has the same sections, in the same order:
  • Capsule ID. A unique identifier for this capsule, starting cap_.
  • Current state. What Closient already has, so the agent does not redo finished work. For example, the brands and product count in your organization.
  • Your task. The steps to follow, and what to ask you before starting. Agents are told to use only values from your own website and files, never to guess a barcode, and to confirm with you before saving anything they are unsure about.
  • How to connect. The MCP server command (preferred) and the REST API fallback.
  • Reference. A link to the matching Agent Skill with full documentation for the workflow.
  • Acceptance criteria. Checks the agent can run to confirm it finished.

Security

  • A capsule never contains a credential. No password, token, or API key is in the text. Pasting a capsule into an agent does not give it access to your account.
  • The agent connects with OAuth, and you approve it. When the agent adds the Closient MCP server, your browser opens Closient’s consent screen. The agent gets access only after you approve it there. See MCP Authentication.
  • The REST fallback is also yours to grant. If the agent uses the REST API instead, the capsule asks you to create an API key yourself. Closient never sends one to the agent.
  • Agents act on your behalf. Closient records both the agent and the user it acts for. See MCP Identity Propagation.
Read the capsule before you paste it, and read your agent’s plan before you let it save. Capsules tell agents to check with you, but you are the final reviewer.

For agent authors

If your agent receives a capsule:
  • Send the capsule’s ID on every Closient API call you make while doing that work, in the X-Closient-Capsule-Id header. Closient uses it to connect your requests to the capsule they came from. A value that is not in the cap_ format is ignored and never causes a request to fail.
  • The capsule links to the skill for its workflow. All skills are listed at /.well-known/agent-skills/index.json, and are documented in Agent Skills.
  • Prefer the MCP path when the capsule offers it. See Install the Closient MCP Server.