Elastic Observability · Agentic Access

Elastic Observability Agentic Access

x-agentic-access generated

Elastic Observability exposes 14 API operations that an AI agent could call, of which 11 are state-changing ‘acting’ operations. This is a recommended x-agentic-access execution contract — the scope, audience, consequence tier, short-lived token constraints, and escalation each action should carry before it is handed to an autonomous agent.

By consequence: 3 read and 11 write.

Contracts are classified heuristically from the provider’s OpenAPI and refresh on every APIs.io network build; audience is bound per deployment. The model follows Curity’s Access Intelligence (apidays Munich 2026). Browse every provider’s agent contracts at agentic-access.apis.io.

AIOpsObservabilityAPMLoggingMetricsTracingOpenTelemetryMonitoringTelemetry
Operations: 14 Acting: 11 Human-in-the-loop: 0 Method: generated

By consequence

read 3 write 11

Source

Agentic Access

Raw ↑ 
generated: '2026-08-29'
method: generated
source: openapi/elastic-observability-agent-config-api-openapi.yml, openapi/elastic-observability-event-intake-api-openapi.yml,
  openapi/elastic-observability-opentelemetry-intake-api-openapi.yml, openapi/elastic-observability-server-info-api-openapi.yml
description: Recommended x-agentic-access execution contracts, classified heuristically from the OpenAPI.
  A governance starting point for exposing this API to AI agents — review and bind audience per deployment.
  See research/curity/agentic-governance/.
summary:
  operations: 14
  by_action_class:
    connected: 3
    acting: 11
  by_consequence:
    read: 3
    write: 11
  human_in_the_loop_required: 0
operations:
- path: /config/v1/agents
  method: get
  operationId: getAgentConfig
  x-agentic-access:
    action-class: connected
    consequence: read
    subject: optional
    token:
      max-ttl: 3600
    audit: none
- path: /config/v1/agents
  method: post
  operationId: postAgentConfig
  x-agentic-access:
    action-class: acting
    consequence: write
    subject: required
    audience: null
    token:
      max-ttl: 900
    escalation:
      human-in-the-loop: conditional
      triggers:
      - abnormal
      - high-value
    audit: required
- path: /config/v1/rum/agents
  method: get
  operationId: getRumAgentConfig
  x-agentic-access:
    action-class: connected
    consequence: read
    subject: optional
    token:
      max-ttl: 3600
    audit: none
- path: /intake/v2/events
  method: post
  operationId: postEventIntake
  x-agentic-access:
    action-class: acting
    consequence: write
    subject: required
    audience: null
    token:
      max-ttl: 900
      purpose-required: true
    escalation:
      human-in-the-loop: conditional
      triggers:
      - abnormal
      - high-value
    audit: required
    x-corrected: consequence lowered from physical to write — see corrections
- path: /intake/v2/rum/events
  method: post
  operationId: postRumEventIntakeV2
  x-agentic-access:
    action-class: acting
    consequence: write
    subject: required
    audience: null
    token:
      max-ttl: 900
      purpose-required: true
    escalation:
      human-in-the-loop: conditional
      triggers:
      - abnormal
      - high-value
    audit: required
    x-corrected: consequence lowered from physical to write — see corrections
- path: /intake/v3/rum/events
  method: post
  operationId: postRumEventIntakeV3
  x-agentic-access:
    action-class: acting
    consequence: write
    subject: required
    audience: null
    token:
      max-ttl: 900
      purpose-required: true
    escalation:
      human-in-the-loop: conditional
      triggers:
      - abnormal
      - high-value
    audit: required
    x-corrected: consequence lowered from physical to write — see corrections
- path: /opentelemetry.proto.collector.metrics.v1.MetricsService/Export
  method: post
  operationId: postOtlpGrpcMetrics
  x-agentic-access:
    action-class: acting
    consequence: write
    subject: required
    audience: null
    token:
      max-ttl: 900
      purpose-required: true
    escalation:
      human-in-the-loop: conditional
      triggers:
      - abnormal
      - high-value
    audit: required
    x-corrected: consequence lowered from physical to write — see corrections
- path: /opentelemetry.proto.collector.trace.v1.TraceService/Export
  method: post
  operationId: postOtlpGrpcTraces
  x-agentic-access:
    action-class: acting
    consequence: write
    subject: required
    audience: null
    token:
      max-ttl: 900
      purpose-required: true
    escalation:
      human-in-the-loop: conditional
      triggers:
      - abnormal
      - high-value
    audit: required
    x-corrected: consequence lowered from physical to write — see corrections
- path: /opentelemetry.proto.collector.logs.v1.LogsService/Export
  method: post
  operationId: postOtlpGrpcLogs
  x-agentic-access:
    action-class: acting
    consequence: write
    subject: required
    audience: null
    token:
      max-ttl: 900
      purpose-required: true
    escalation:
      human-in-the-loop: conditional
      triggers:
      - abnormal
      - high-value
    audit: required
    x-corrected: consequence lowered from physical to write — see corrections
- path: /v1/metrics
  method: post
  operationId: postOtlpHttpMetrics
  x-agentic-access:
    action-class: acting
    consequence: write
    subject: required
    audience: null
    token:
      max-ttl: 900
      purpose-required: true
    escalation:
      human-in-the-loop: conditional
      triggers:
      - abnormal
      - high-value
    audit: required
    x-corrected: consequence lowered from physical to write — see corrections
- path: /v1/traces
  method: post
  operationId: postOtlpHttpTraces
  x-agentic-access:
    action-class: acting
    consequence: write
    subject: required
    audience: null
    token:
      max-ttl: 900
      purpose-required: true
    escalation:
      human-in-the-loop: conditional
      triggers:
      - abnormal
      - high-value
    audit: required
    x-corrected: consequence lowered from physical to write — see corrections
- path: /v1/logs
  method: post
  operationId: postOtlpHttpLogs
  x-agentic-access:
    action-class: acting
    consequence: write
    subject: required
    audience: null
    token:
      max-ttl: 900
      purpose-required: true
    escalation:
      human-in-the-loop: conditional
      triggers:
      - abnormal
      - high-value
    audit: required
    x-corrected: consequence lowered from physical to write — see corrections
- path: /
  method: get
  operationId: getServerHealth
  x-agentic-access:
    action-class: connected
    consequence: read
    subject: optional
    token:
      max-ttl: 3600
    audit: none
- path: /
  method: post
  operationId: postServerHealth
  x-agentic-access:
    action-class: acting
    consequence: write
    subject: required
    audience: null
    token:
      max-ttl: 900
    escalation:
      human-in-the-loop: conditional
      triggers:
      - abnormal
      - high-value
    audit: required
corrections:
- date: '2026-08-29'
  applied_to:
  - postEventIntake
  - postRumEventIntakeV2
  - postRumEventIntakeV3
  - postOtlpGrpcMetrics
  - postOtlpGrpcTraces
  - postOtlpGrpcLogs
  - postOtlpHttpMetrics
  - postOtlpHttpTraces
  - postOtlpHttpLogs
  from: physical
  to: write
  reason: The derive heuristic raises consequence to `physical` on payment/order/transfer style keywords,
    and it fired on the telemetry intake and OTLP *Export* operation names. Writing a span, a metric
    sample or a log line into an observability store moves no money and touches no physical system —
    it is an ordinary append. Left uncorrected this file would tell an agent it needs token exchange
    and a stated purpose to emit a log, which is both wrong and the kind of false ceiling that gets
    governance guidance ignored wholesale.
  residual_risk: 'These operations remain `acting`/`write` with audit: required, which is correct: the
    writes are irreversible and un-deduplicated. See conventions/elastic-observability-conventions.yml
    reversibility.'

Work with this as data

Every access contract here is available over the APIs.io API and to AI agents over MCP. Agentic Access is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for agentic access

3 MCP tools reach this
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
Search the catalog 
curl "https://apis.io/api/v1/search?q=elastic-observability-agentic-access&limit=10"
Everything under a tag 
curl "https://apis.io/api/v1/tags/elastic-observability-agentic-access"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.