Introduction

Your agents should work like AGI

Your users don’t care about your agent’s architecture. They care that it handles their request — whatever it is, however messy it gets. Connect their CRM, resize an image, pull data from behind OAuth, recover when a service goes down. That’s the AGI experience: an agent that just figures it out.

Ploton is the infrastructure layer that makes this possible. One API call, and your agent can authenticate users, connect third-party services, fetch live data, and recover from failures — without a human in the loop.

curl -X POST https://api.ploton.ai/v1/tasks \
  -H "Authorization: Bearer $PLOTON_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "prompt": "Connect the user'\''s CRM account and pull contacts created this month",
    "user_id": "user_123"
  }'

Your agent describes what needs to happen. Ploton figures out the how — runs the OAuth flow, stores credentials, calls the right API, handles pagination and rate limits, and delivers structured data back via webhook. Your agent never touches a redirect URL or a retry loop.

The gap between demo and production

AI agents are great at reasoning. They fall apart the moment they need to do something in the real world:

• Authentication — OAuth flows, token refresh, credential storage. Every service works differently. Your agent shouldn’t have to care.
• User interaction — Approvals, missing data, preference collection. The agent needs to ask a human and wait, not crash.
• Failure recovery — Expired tokens, rate limits, schema changes, service outages. Production agents need to recover on their own.

Most teams spend weeks writing this plumbing for every integration, every edge case, every service. And it’s never done — new things keep breaking. That’s time you’re not spending on the product your users actually see.

Ploton handles the messy parts so your agent ships like AGI from day one.

How it works

sequenceDiagram
    participant Agent
    participant Ploton
    participant Services

    Agent->>Ploton: Task prompt
    Ploton->>Ploton: Select tools & build workflow
    Ploton->>Services: Authenticate & execute
    Services-->>Ploton: Result
    Ploton-->>Agent: Webhook with structured data

1. Your agent hits a roadblock

Mid-task, your agent needs something it can’t do alone — connect a user’s payment account, send a transactional email, pull data from behind OAuth.

2. Your agent calls Ploton

One HTTP request with a natural language prompt. No SDK required, no workflow definition, no DAG.

curl -X POST https://api.ploton.ai/v1/tasks \
  -H "Authorization: Bearer $PLOTON_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "prompt": "Send an invoice email to user_123 using the monthly_invoice template. Attach their latest PDF invoice.",
    "user_id": "user_123"
  }'

Ploton reads the prompt, picks the right tools, pulls from past execution data, builds a workflow, and runs it.

3. Ploton delivers the result

Your agent gets structured data back via webhook. No polling required, though you can poll if you prefer.

{
	"event": "task.complete",
	"task_id": "task_8xK2mP",
	"timestamp": "2025-06-15T14:22:03Z",
	"data": {
		"email_id": "sg_msg_4f9a2c",
		"delivered_to": "jane@acme.com",
		"template": "monthly_invoice",
		"attachment": "inv_2025_06.pdf"
	}
}

This typically completes in seconds. Your agent isn’t blocked while it runs.

Key concepts

Tools

Tools are the external things Ploton connects to — a database, CRM, payment processor, internal API, shell command. Ploton handles auth, invocation, and error handling for each one.

Learn more about Tools

Tasks

A task is one prompt, one unit of work. Your agent describes what it needs in plain language, and Ploton builds and runs a workflow to get it done. A single task might invoke multiple tools across multiple steps, but from your agent’s perspective it’s one request.

Learn more about Tasks

Trained tasks

Every time a task runs, Ploton records what worked, what failed, how it recovered, and where rate limits hit. That execution history makes future runs faster and more reliable.

Learn more about Trained Tasks

Workflows

Ploton doesn’t use rigid DAGs. Each task generates its own workflow at runtime — the steps, the tools, the execution order. If a step fails, the workflow adapts instead of crashing.

Learn more about Workflows

Webhooks

Results come back asynchronously via HTTP POST to your configured endpoint. Your agent fires a task and moves on. Ploton calls back when it has something to report.

Learn more about Webhooks

Why Ploton?

Next steps

• Quickstart — Create your first task in under 5 minutes
• Trained Tasks — How tasks get smarter over time
• API Overview — Explore the REST API