Agent & API observability

See whatyour agentsare doing.

Turn connected API and MCP traffic into an inventory you can explore, activity you can investigate, and access decisions you can manage. Built around the gateways you already use.

MVP · Lab-validated integrations · Ready for evaluation
Self-hosted collectionFree Altprobe packageREST · MCP · A2A
Context, connected.
sample-stack / activityILLUSTRATIVE DATA
Follow the interactionCONNECTED TELEMETRY
HTTP telemetry AI agent research-agent Gateway authenticated identity MCP server tools/call REST API /api/search Altprobe
Observed callNEW ENDPOINT
research-agent→tools/call→internal-search
Source: gateway telemetryNext: review inventory
An example workflow, not a live product session.API / MCP

Connect to the gateway
you already run.

APISIXenvoyOpenRestyKONGtraefikHigress
Visibility that leads somewhere

Less guesswork.
More context.

Understand what is connected, what changed, and which activity needs a closer look.

01 / DISCOVER

Discover new interfaces

Build an inventory of REST endpoints, MCP tools and A2A metadata seen in connected telemetry. Review new interfaces and changes against your declared baseline.

Endpoint discoveryInventory drift
02 / INVESTIGATE

Investigate with context

Follow captured calls and responses. Bring related gateway, Falco and Suricata events together to understand the evidence behind a finding.

Execution tracesRelated events
03 / CONTROL

Make access deliberate

Bind a subject to its authenticated gateway identity. Manage agent and endpoint access in Alertflex, with recorded decisions and enforcement through configured gateway routes.

Access decisionsAudit trail

From events to a clearer picture.

ACTUAL OPENSEARCH DASHBOARDS · LAB DATA

Two products. One connected workflow.

Collect with Altprobe.
Put context to work with Alertflex.

Start with telemetry and OpenSearch. Add the Alertflex console when your team needs shared inventory, traces and access management.

Your connected infrastructure
API / AI GatewayFalcoSuricataTrivy / SBOM
AltprobeCollect · Normalize · Correlate
OpenSearchSearch, findings
and dashboards
AlertflexInventory, traces
and access decisions
↖ Configured Policy decisions return to the gateway
01

Connect the sources

Gateway logs and supported connectors bring HTTP activity into Altprobe. Add Falco or Suricata events where you need host and network context.

02

Create a common view

Altprobe normalizes supported events into OCSF for OpenSearch and supplies observed inventory and matched traces to Alertflex.

03

Add software context

Import CycloneDX reports from configured Trivy scans of projects or container images. Explore component inventory in Alertflex and vulnerability findings in OpenSearch.

04

Review and act

Use the console to inspect evidence and set access decisions. A local Policy listener supplies decisions to protected gateway routes.

Telemetry analysis is asynchronous. Policy authorization is a separate, synchronous path on configured routes; console changes take effect after inventory polling.

Fits the stack you have

Your gateway.
A connected view.

Six gateway labs and reusable connectors. Choose a familiar entry point and build from there.

Add context when you need it
FalcoSuricataTrivyOWASP CRS
RESTMCPA2A
Start small. Expand with purpose.

Try the technology.
Then make it yours.

Evaluate with local, synthetic traffic before connecting your own environment.

THE COLLECTORFREE · APACHE 2.0

Start with Altprobe.

A ready-to-run Linux collector, reusable integrations and OpenSearch dashboards. Get a working lab without an Alertflex account.

  • Six self-contained gateway labs
  • Shared tests and synthetic traffic
  • OCSF output and CycloneDX SBOM findings
START WITH APISIX
git clone https://github.com/olegzhr/altprobe.git
THE PLATFORMGUIDED EVALUATION

Bring your team into the picture.

Use Alertflex to organize observed assets, examine traces and incidents, and manage configured access decisions from one console.

  • Agent, API, MCP and A2A inventory
  • Incident evidence and decision history
  • Gateway identity binding and access controls
  • Deployment planning and integration support

No one-size-fits-all promise. We scope a deployment around your sources, topology and operating requirements.

A few practical answers

Know what
you are starting with.

A clear scope makes a better evaluation. Here is how the pieces fit together.

Have a different question?
What can I use for free?

Altprobe collector binaries, connectors and labs are available under Apache-2.0. You can evaluate collection, OCSF output and dashboards locally. Contact us to discuss Alertflex deployment and support.

What activity can Alertflex see?

Visibility depends on the sources you connect and the fields they capture. Supported gateway integrations expose network-based API and MCP interactions.

Is everything in the request path?

No. Telemetry analysis runs after capture. When you enable Policy for protected routes, the gateway makes a separate synchronous authorization call. A finding raised later cannot undo an already completed request. Inventory polling also means a console change is not applied instantly.

Where does the data go?

Altprobe can run in your environment and send supported events to your OpenSearch deployment. Alertflex receives the inventory, traces and incident data enabled in your configuration.

How should we evaluate it?

Start with one of the six gateway labs and its shared tests. Then run a scoped pilot on representative traffic.

Make the next interaction visible

Your agents are already working.
Let’s make their activity understandable.

Tell us about your gateways, agents and deployment needs. We will help define a focused first step.