Use Tryr with your AI agent
Give your agent a product URL. It can start a shoot and bring you the finished frames. Your account and credits stay the same.
How it works22 seconds: get a key, connect your agent, give it a product link.
Create a key
The key belongs to your account; your agent works with your credits.
- Open your dashboard and sign in.
- Under Agent access, select Create API key. The key (
tryr_sk_…) is displayed only once. - Keep it private. If it is exposed, revoke it in the same section.
Connect your agent
Pick your client, copy the snippet and replace tryr_sk_... with your key.
Run it in your terminal.
claude mcp add --transport http tryr https://tryr.app/mcp \
--header "Authorization: Bearer tryr_sk_..."Other MCP clients use the same shape (mcp.json).
{
"mcpServers": {
"tryr": {
"url": "https://tryr.app/mcp",
"headers": { "Authorization": "Bearer tryr_sk_..." }
}
}
}~/.gemini/settings.json
{
"mcpServers": {
"tryr": {
"httpUrl": "https://tryr.app/mcp",
"headers": { "Authorization": "Bearer tryr_sk_..." }
}
}
}~/.codex/config.toml; the key is read from the environment: export TRYR_API_KEY=tryr_sk_...
[mcp_servers.tryr]
url = "https://tryr.app/mcp"
bearer_token_env_var = "TRYR_API_KEY"
# Read and shoot tools (for unattended runs such as codex exec)
[mcp_servers.tryr.tools.tryr_hesap]
approval_mode = "approve"
[mcp_servers.tryr.tools.tryr_cekimler]
approval_mode = "approve"
[mcp_servers.tryr.tools.tryr_cekim_baslat]
approval_mode = "approve"
[mcp_servers.tryr.tools.tryr_cekim_durumu]
approval_mode = "approve"
[mcp_servers.tryr.tools.tryr_cevapla]
approval_mode = "approve"
[mcp_servers.tryr.tools.tryr_onayla]
approval_mode = "approve"
[mcp_servers.tryr.tools.tryr_kare_onizle]
approval_mode = "approve"Interactive Codex asks before each tool call. In unattended runs such as codex exec, starting a shoot is rejected with "MCP tool call requires approval" unless these lines are present. We do not recommend auto-approving tryr_kare_indir (spends credits) or tryr_paketler and tryr_kredi_al (create payment links). Do not call tryr_onayla before the first frames are ready; an early call returns not_ready. Frames take one to a few minutes; polling the status every 10 to 20 seconds is enough.
Custom GPT Actions: Import https://tryr.app/agent/v1/openapi.json as the schema. For authentication, choose API Key → Bearer and enter your key.
claude.ai and ChatGPT connectors (account sign-in via OAuth): coming soon.
Ask
Give your agent a product URL. It starts the shoot, goes through the questions with you and brings back the frames.
Your agent does not forward a short request as is. It reads the product page and the questions, writes a concrete brief covering setting, light, framing and what to avoid, shows it to you briefly, and sends the version you approve or edit. You always have the final say; nothing the product does not have is added.
Film: two-step approval
Start returns a film plan and credit quote without spending credits or free storyboard allowance. You approve the price separately; approval charges once. An insufficient balance returns 402 with an explanation.
- MCP
tryr_film_baslat→tryr_film_onayla→tryr_film_durumu→tryr_film_indir. Status tools acceptwait_secondsup to 50.- CLI
tryr film start <shoot-id> --duration 15 --tier 720p,tryr film approve <shoot-id> <film-id>,tryr film status <shoot-id> <film-id> --wait,tryr film download <shoot-id> <film-id>- REST
POST /agent/v1/shoots/{id}/films→POST /agent/v1/shoots/{id}/films/{film}/approve→GET /agent/v1/shoots/{id}/films/{film}?wait_seconds=50→GET /agent/v1/shoots/{id}/films/{film}/download
Terminal (CLI)
The CLI package has not been published to npm yet. Until then, use MCP or the REST API.
CLI commands support --json for machine-readable output and can read your key from the TRYR_API_KEY environment variable.
REST API
curl -X POST https://tryr.app/agent/v1/shoots \
-H "Authorization: Bearer tryr_sk_..." \
-H "Content-Type: application/json" \
-d '{"url":"https://store.example/product"}'| Endpoint | Purpose |
|---|---|
GET /agent/v1/me | Account, credits, and pricing |
POST /agent/v1/shoots | Start a shoot from a product URL |
GET /agent/v1/shoots/{id} | Status, questions, frames, and next step |
POST /agent/v1/shoots/{id}/answers | Answer questions (empty body uses defaults) |
POST /agent/v1/shoots/{id}/approve | Generate the remaining planned scenes |
GET /agent/v1/shoots/{id}/frames/{n}/preview | Free preview (720 px) |
GET /agent/v1/shoots/{id}/frames/{n} | Download a full-resolution frame (uses credits) |
GET /agent/v1/plans | Credit packages and prices |
POST /agent/v1/checkout | Create a package checkout link |
Full schema: /agent/v1/openapi.json. Write endpoints accept the Idempotency-Key header.
Buying credits
When credits run out, your agent can list packages and give you a Stripe checkout link. You complete payment yourself. The agent never sees your card details or charges you directly. Credits are added to your account after payment.
- MCP:
tryr_paketler→tryr_kredi_al(package and term) → open the link →tryr_hesap - CLI:
tryr plans,tryr buy baslangic --term aylik --open - REST:
GET /agent/v1/plans,POST /agent/v1/checkout {"package":"baslangic","term":"aylik"}→checkout_url
Packages are subscriptions and renew until canceled; 20% of unused subscription credits roll over to the next period. To cancel, use your panel or contact info@agentized.io. Details: Terms of Service.
Costs and limits
- Starting a shoot and reading the product are free. Answering the questions starts generation: every image, including the first two previews, costs its size price in credits (1K/2K 2, 4K 5). A low balance returns
402 plan_gerekli. - A frame is paid when it is generated; a download only costs the size difference (download price 1K 2, 2K 3, 4K 5 minus what was paid), and downloading the same frame again does not charge you twice. Current pricing is included in
GET /agent/v1/me. - Agent keys open and work only on accounts that have made a purchase (a plan or a credit top-up); purchasing accounts have no shoot limits.
For bulk use and integrations: info@agentized.io