How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Amigo Agents API

The Agents API from Amigo — 4 operation(s) for agents.

Amigo Agents API is one of 72 APIs that Amigo publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Agents. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 8 operations across 4 paths, and defines 17 schemas. It is described by OpenAPI 3.2.0, at version 0.1.0.

Requests are made against 5 base URLs: https://api.amigo.ai, https://internal-api.amigo.ai, https://api-eu-central-1.amigo.ai, https://api-ap-southeast-2.amigo.ai, https://api-ca-central-1.amigo.ai.

8 operations 4 paths 17 schemas 1 DELETE4 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0
Base URL
https://api.amigo.ai
Authentication
HTTP Bearer, API Key, HTTP Basic
Resource Areas
1

Authentication & Security 3

Amigo Agents API declares 3 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (Bearer-Authorization). An API key is passed in the header as X-ORG-ID (Bearer-Authorization-Organization). It accepts HTTP basic authentication (Basic). By default, every request must be authenticated.

  • Bearer-Authorization — Amigo issued JWT token that identifies an user. It's issued either after logging in through the frontend, or manually through the [SignInWithAPIKey](sign-in-wi…
  • Bearer-Authorization-Organization — An optional organization identifier that indicates from which organization the token is issued. This is used in rare cases where the user to authenticate is ma…
  • Basic — The username should be set to {orgid}{userid}, and the password should be the Amigo issued JWT token that identifies the user.

Paths & Operations 8

Across 4 paths, the API surfaces 8 operations — 1 DELETE, 4 GET, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Agents 8
POST
/v1/{workspace_id}/agents
Create an agent
create-agent 1 param body → 201404409403401422
GET
/v1/{workspace_id}/agents
List agents
list-agents 5 params → 200404403401422
GET
/v1/{workspace_id}/agents/{agent_id}
Get an agent
get-agent 2 params → 200404403401422
PUT
/v1/{workspace_id}/agents/{agent_id}
Update an agent
update-agent 2 params body → 200404409403401422
DELETE
/v1/{workspace_id}/agents/{agent_id}
Delete an agent
delete-agent 2 params → 204404403401422
POST
/v1/{workspace_id}/agents/{agent_id}/versions
Create an agent version
create-agent-version 2 params body → 201404409403401422
GET
/v1/{workspace_id}/agents/{agent_id}/versions
List agent versions
list-agent-versions 5 params → 200404403401422
GET
/v1/{workspace_id}/agents/{agent_id}/versions/{version}
Get an agent version
get-agent-version 3 params → 200404403401422

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are AgentVersionResponse (13 properties), VoiceConfig (8 properties), CreateAgentVersionRequest (7 properties), AgentResponse (7 properties). Each schema is shown below with its type and property counts.

PaginatedResponse_AgentVersionResponse_
object
4 properties 2 required
Identity
object
5 properties 4 required
NameString
string
AgentVersionResponse
object
13 properties 13 required
HTTPValidationError
object
1 property
DescriptionString
string
LanguageProviderEntry
object
Per-language TTS provider configuration.
2 properties 1 required
BackgroundString
string
PaginatedResponse_AgentResponse_
object
4 properties 2 required
SearchString
string
CreateAgentVersionRequest
object
7 properties 2 required
VoiceConfig
object
8 properties 1 required
AgentResponse
object
7 properties 6 required
ValidationError
object
5 properties 3 required
CreateAgentRequest
object
2 properties 1 required
UpdateAgentRequest
object
2 properties
RelationshipToDeveloper
object
4 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

amigo-agents-api-openapi.yml Raw ↑

Other APIs Amigo publishes across the network.

Amigo Account API
Amigo Admin API
Amigo Agent Definitions API
Amigo Agent Runs API
Amigo Analytics API
Amigo API Keys API
Amigo Audit API
Amigo Auth API
Amigo Billing API
Amigo Calls API
Amigo Command Center API
Amigo Compliance API
Where this information came from

This is an independent, third-party profile of Amigo Agents API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.