GET request.
Agents run primarily via browser-use, along with other AI tools. Additionally, agents may be configured to use MCP servers to expand capabilities.
Core capabilities include:
- Create, list, update, or delete persistent agents.
- Run on a schedule using cron-like strings (
@daily,@every 30m, or full cron expressions). - Activate/deactivate agents without losing configuration.
- Send messages and fetch timelines to drive conversational workflows.
- Inspect processing state and recent browser tasks tied to the agent.
- Receive structured data as a response
Base path
All persistent agent routes live under/api/v1/agents/.
- Production:
https://gobii.ai/api/v1/agents/ - Self-hosted/local:
http://localhost:8000/api/v1/agents/
X-Api-Key: <api_key>).
Resource shape
Key fields you will see in responses:id(UUID): Agent identifier used in all routes.name(string): Display name. Must be unique per user or organization.charter(string): Free-form instructions for what the agent should do.schedule(string|null): Cron-like schedule such as@dailyor0 */4 * * *. Omit ornullfor manual-only agents.is_active(bool): Whether the agent currently runs or responds.life_state(enum):activeorexpired(soft pause due to inactivity).whitelist_policy(enum): Controls who can message the agent (defaultormanual).preferred_contact_endpoint_id(UUID|null): Default email/SMS endpoint the agent uses to reach you.browser_use_agent_id(UUID): The underlying browser automation worker.available_mcp_servers/personal_mcp_server_ids(arrays): MCP server metadata and enabled personal servers.- Timestamps:
created_at,updated_at,last_interaction_at.
Endpoint summary
GET /agents/— List agents (paginated).POST /agents/— Create an agent.GET /agents/{id}/— Retrieve details.PATCH /agents/{id}/— Partial update (name, charter, schedule, whitelist policy, preferred contact, MCP servers, etc.).DELETE /agents/{id}/— Delete an agent.POST /agents/{id}/activate/— Mark active (also clearslife_state=expired).POST /agents/{id}/deactivate/— Pause without deleting.GET /agents/{id}/processing-status/— Check whether the agent is currently processing work.POST /agents/{id}/schedule/preview/— Validate a cron-like schedule and get a human-readable description.GET /agents/{id}/timeline/— Scrollable list of recent message/task events.POST /agents/{id}/messages/— Inject an inbound email/SMS message into the agent.GET /agents/{id}/web-tasks/?limit=50&status=complete— Recent browser tasks executed by this agent.
Create an agent
Retrieve or list agents
List your agents (default page size 10, use?page_size= to increase up to 100):
Update or pause
Patch mutable fields such asname, charter, schedule, whitelist_policy, or contact preferences:
Messaging and timelines
Send an inbound message (email or SMS) into the agent’s conversation thread:recipient to use the agent’s primary email or SMS endpoint by default.
Fetch the event timeline (message history plus processing markers).