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

Relevance AI Agents API

The Agents API from Relevance AI — 7 operation(s) for agents.

Relevance AI Agents API is one of 32 APIs that Relevance AI 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, API documentation, an API reference, and authentication docs.

This API exposes 7 operations across 7 paths, and defines 13 schemas. It is described by OpenAPI 3.2.0, at version latest.

Requests are made against a single base URL, /latest.

7 operations 7 paths 13 schemas 2 DELETE1 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
latest
Base URL
https://api-{region}.stack.tryrelevance.com/latest
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Relevance AI Agents API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (AuthorizationHeader). By default, every request must be authenticated.

  • AuthorizationHeader — Authorization credentials. Header authorization should be in the form of: project:apikey

Paths & Operations 7

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

Agents 7
DELETE
/agents/{agent_id}/conversations
DeleteAgentConversations
DeleteAgentConversations 1 param body → 200
DELETE
/agents/{agent_id}/conversations/{conversation_id}
DeleteAgentConversation
DeleteAgentConversation 2 params body → 200
POST
/agents/{agent_id}/tags/upsert
UpsertUserAgentTag
UpsertUserAgentTag 1 param body → 200
POST
/agents/{agent_id}/tags/delete
DeleteUserAgentTag
DeleteUserAgentTag 1 param body → 200
GET
/user_tags/list
ListUserTags
ListUserTags → 200
POST
/user_tags/upsert
UpsertUserTag
UpsertUserTag body → 200
POST
/user_tags/delete
DeleteUserTag
DeleteUserTag body → 200

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are UpsertUserTagInput (3 properties), DeleteAgentConversationsInput (1 property), ListUserTagsOutput (1 property), UpsertUserTagOutput (1 property). Each schema is shown below with its type and property counts.

DeleteAgentConversationsInput
object
1 property 1 required
DeleteAgentConversationInput
object
DeleteAgentConversationOutput
object
DeleteAgentConversationsOutput
object
DeleteUserTagOutput
object
DeleteUserTagInput
object
1 property 1 required
DeleteUserAgentTagInput
object
1 property 1 required
UpsertUserTagOutput
object
1 property 1 required
UpsertUserTagInput
object
3 properties 2 required
ListUserTagsOutput
object
1 property 1 required
UpsertUserAgentTagOutput
object
DeleteUserAgentTagOutput
object
UpsertUserAgentTagInput
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

relevance-ai-agents-api-openapi.yml Raw ↑

Other APIs Relevance AI publishes across the network.

Relevance AI MCP Server
Relevance AI Agent Debug Configs API
Relevance AI Agent Runtime Events API
Relevance AI Alarms API
Relevance AI Analytics API
Relevance AI Apify API
Relevance AI Auth API
Relevance AI Billing API
Relevance AI Branding Kit API
Relevance AI Branding Kits API
Relevance AI Chat API
Relevance AI Evals API
Where this information came from

This is an independent, third-party profile of Relevance AI 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.