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

Voyant.io DEO Signals API

Developer Experience Optimization - track AI agent interactions, RAG queries, and tool integrations with your content.

Voyant.io DEO Signals API is one of 99 APIs that Voyant.io publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include DEO Signals. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 10 operations across 10 paths, and defines 18 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://voice-forge-production.up.railway.app.

10 operations 10 paths 18 schemas 5 GET5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://voice-forge-production.up.railway.app
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Voyant.io DEO Signals API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (HTTPBearer).

Paths & Operations 10

Across 10 paths, the API surfaces 10 operations — 5 GET, 5 POST. Each is listed below with its method, path, parameters, and response codes.

DEO Signals 10

Developer Experience Optimization - track AI agent interactions, RAG queries, and tool integrations with your content.

POST
/api/deo/ingest
Ingest Deo Events
ingest_deo_events_api_deo_ingest_post body → 200422
GET
/api/deo/agents
List Agents
list_agents_api_deo_agents_get 4 params → 200422
GET
/api/deo/stats
Get Dashboard Stats
get_dashboard_stats_api_deo_stats_get 1 param → 200422
GET
/api/deo/interactions
List Interactions
list_interactions_api_deo_interactions_get 4 params → 200422
POST
/api/deo/sources/register
Register Deo Source
register_deo_source_api_deo_sources_register_post 3 params → 200422
GET
/api/deo/sources
List Deo Sources
list_deo_sources_api_deo_sources_get → 200
POST
/api/deo/v1/traces
Ingest Otlp Traces
ingest_otlp_traces_api_deo_v1_traces_post body → 200422
POST
/api/deo/mcp-telemetry
Ingest Mcp Telemetry
ingest_mcp_telemetry_api_deo_mcp_telemetry_post body → 200422
POST
/api/deo/v1/telemetry/events
Ingest Mcp Telemetry
ingest_mcp_telemetry_api_deo_v1_telemetry_events_post body → 200422
GET
/api/deo/funnel
Get Journey Funnel
get_journey_funnel_api_deo_funnel_get 1 param → 200422

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are DEOEventPayload (16 properties), DEOIngestRequest (12 properties), AgentSummary (10 properties), DEODashboardStats (9 properties). Each schema is shown below with its type and property counts.

MCPEventContext
object
Context from standard MCP telemetry format
4 properties 2 required
AgentSummary
object
Summary of an AI agent
10 properties 9 required
DEOIngestRequest
object
Batch ingest request from an instrumented source
12 properties 4 required
MCPTelemetryEvent
object
Single event in standard MCP telemetry format
3 properties 3 required
DEODashboardStats
object
Dashboard statistics
9 properties 9 required
MCPEventData
object
Event data from standard MCP telemetry format
5 properties 2 required
ValidationError
object
5 properties 3 required
OTLPTraceRequest
object
OTLP/JSON trace export request
1 property
HTTPValidationError
object
1 property
DEOIngestResponse
object
Response from ingest endpoint
6 properties 4 required
OTLPResourceSpans
object
OTLP resource with scope spans
2 properties
OTLPSpan
object
OTLP span
9 properties 4 required
MCPTelemetryRequest
object
Standard MCP telemetry batch request. This is the format used by instrumented MCP servers. Any MCP server can use this format to report telemetry.
4 properties 1 required
OTLPScope
object
OTLP instrumentation scope
2 properties
OTLPScopeSpans
object
OTLP scope with spans
2 properties
OTLPResource
object
OTLP resource
1 property
OTLPAttribute
object
OTLP attribute value wrapper
2 properties 2 required
DEOEventPayload
object
Single DEO event from an instrumented touchpoint
16 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

voyant-deo-signals-api-openapi.yml Raw ↑

Other APIs Voyant.io publishes across the network.

Voyant MCP Server
Voyant.io Admin API
Voyant.io Admin Migration API
Voyant.io AI Assistant API
Voyant.io Airops API
Voyant.io Analytics API
Voyant.io API Keys API
Voyant.io Attribution API
Voyant.io Attribution Intelligence API
Voyant.io Auth API
Voyant.io Battlecards API
Voyant.io Bootstrap API
Where this information came from

This is an independent, third-party profile of Voyant.io DEO Signals 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.