Discover the workspace
List connected Pinterest accounts, sync boards, and inspect sections as structured JSON before the agent makes a decision.
pinapex boards list <accountId> --sync --jsonPinapex lets agents discover the right account, publish or schedule Pins, manage the queue, and bring analytics back into the next decision—all through a secure CLI and API.
Pinterest OAuth · Revocable team token · JSON output · No database secrets
$ pinapex accounts list --json{ "id": "acct_01", "name": "North & Pine", "status": "active" }$ pinapex boards list acct_01 --sync --json{ "boards": ["Spring Ideas", "Small Spaces", "Weekend Projects"] }$ pinapex pins publish --account acct_01 \
--board "Spring Ideas" --image ./pin.jpg \
--schedule 2026-09-02T09:00:00Z --jsonFrom prompt to published Pin
Writing a caption is one step. Pinapex exposes the operational context and actions around it, so an agent can finish the job and verify what happened.
List connected Pinterest accounts, sync boards, and inspect sections as structured JSON before the agent makes a decision.
pinapex boards list <accountId> --sync --jsonChoose the correct account and board, upload a local asset or URL, then publish immediately or schedule an exact ISO time.
pinapex pins publish … --schedule <iso8601> --jsonInspect status, change copy or timing while a Pin is queued, cancel work, and surface delivery errors without opening another tab.
pinapex queue list --status queued --jsonSync impressions, saves, Pin clicks, and outbound clicks so the next content decision starts with current performance data.
pinapex analytics summary --days 30 --jsonAgentic by architecture
The model never needs your Pinterest password or infrastructure credentials. It expresses an action; Pinapex authenticates, scopes, validates, executes, and reports the result.
Campaign goal, creative, timing, and guardrails.
Accounts, boards, sections, queues, and recent results.
Team scope, OAuth, validation, and official API delivery.
Status and metrics feed the next agent decision.
Agent access should be explicit, scoped, observable, and reversible. That boundary is part of the product—not a prompt you hope the model follows.
Accounts connect through Pinterest OAuth, not shared login credentials.
The CLI is an authenticated HTTP client; it holds no database, storage, or Pinterest app secrets.
Every action is filtered to the token's team on the server. There is no client-side team override.
Revoke a personal access token whenever an agent or machine no longer needs it.
Bring your own agent
Use the Pinapex CLI from a terminal or call the same authenticated actions over HTTP. Structured JSON keeps the workflow portable across agent environments.
Pinterest Agent FAQ
What the agent can do, what it needs, and where control stays with your team.
It is an AI agent that can do operational Pinterest work through defined tools, not merely suggest copy. With Pinapex, an authorized agent can discover accounts and boards, publish or schedule Pins, manage the queue, and read analytics.
Yes. The Pinapex CLI and HTTP API support immediate and scheduled publishing with a Pinterest account, board, image, title, description, destination link, alt text, and optional tags.
No. Pinterest accounts connect through OAuth. The agent receives a revocable, team-scoped Pinapex token; it never needs a Pinterest password, database credential, or storage secret.
The workflow is designed for Claude Code, Codex, ChatGPT, and other agents that can run shell commands or make authenticated HTTP requests. Every command can return machine-readable JSON.
No. A signed-in user can generate a token in the browser, and an agent can call the hosted API from any machine. The CLI is an optional convenience layer over the same authenticated HTTP actions.
Agent-ready from the first account
Connect Pinterest once, give your agent scoped access, and keep every account, action, queue, and result in Pinapex.