covia.ai valid
Covia
The Universal Grid for the Agent Economy. Covia is an open-core, open-source runtime for federated AI orchestration and federated AI execution. A **venue** is a grid node that hosts self-describing **operations**, runs stateful **agents** (Covia Agents: hosted agents, plus BYOA over A2A/MCP and BYOM via pluggable LLM bindings), and keeps an immutable, auditable **job** record for every invocation. Venues federate across organisational boundaries: data stays where it is governed and only results
- Authority
- 50 reach 0 · trust 10 · quality 25 · freshness 15
- Tier
- listed
- llms.txt
- https://docs.covia.ai/llms.txt
- llms-full.txt
- https://docs.covia.ai/llms-full.txt
- Sections
- 6
- Links
- 28
- Size
- 5953 bytes
- Registered
- 2024-05-13
- Country
- United States Hosting inference
- Hosting country
- United States Hosting inference
- Country evidence
- No published address evidence collected yet
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-25T17:02:58.967Z
- Last checked
- 2026-10-25T17:03:08.190Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-25T17:02:59.188Z. Cached copy · Source on covia.ai
# Covia
> The Universal Grid for the Agent Economy. Covia is an open-core, open-source runtime for federated AI orchestration and federated AI execution. A **venue** is a grid node that hosts self-describing **operations**, runs stateful **agents** (Covia Agents: hosted agents, plus BYOA over A2A/MCP and BYOM via pluggable LLM bindings), and keeps an immutable, auditable **job** record for every invocation. Venues federate across organisational boundaries: data stays where it is governed and only results cross. Built on the Convex lattice for content-addressed, cryptographically verifiable state. Speaks REST, MCP, A2A, and DID. Runtime EPL-2.0, SDKs Apache-2.0.
Key facts for agents and tools:
- Every venue serves the same REST API under `/api/v1/` (OpenAPI at `/swagger`). Invoke an operation: `POST /api/v1/invoke` with `{"operation": "v/ops/schema/infer", "input": {...}, "wait": true}`; the response is a job record whose `output` carries the result.
- Operations are addressed by catalog path `v/ops/<adapter>/<op>` (e.g. `v/ops/schema/infer`, `v/ops/langchain/openai`). The short `adapter:op` style seen in prose is a display name only; it is NOT a resolvable reference. List operations: `GET /api/v1/operations`.
- Every venue is an **MCP server** at `POST /mcp` (operations exposed as snake_case tools) and an **A2A v1.0 agent** at `POST /a2a`.
- Machine discovery on every venue: `/.well-known/did.json`, `/.well-known/mcp.json`, `/.well-known/agent-card.json`.
- Live public venues for testing (no signup): https://venue-3.covia.ai and https://venue-4.covia.ai (development build, matches these docs); https://venue-1.covia.ai and https://venue-2.covia.ai (stable release, Google Cloud); https://venue-test.covia.ai (scratch venue, data may be cleared)
- Run your own venue: `docker run -p 8080:8080 ghcr.io/covia-ai/covia:latest` (or `java -jar covia.jar`, Java 21+). `:latest` is the development channel matching these docs; `:stable` is the release build.
- SDKs: TypeScript `@covia/covia-sdk` (npm), Python `covia` (PyPI), Java `ai.covia:covia-core` (build from source).
- Authorisation is capability-based (UCAN): `{with, can}` grants presented as bearer tokens and enforced per call.
- Status: open source (EPL-2.0), pre-1.0; APIs may change.
- All documentation as one markdown file: https://docs.covia.ai/llms-full.txt, and each docs page is mirrored as raw markdown (append `.md` to its path).
## Getting started
- [Overview](https://docs.covia.ai/docs/overview/): What Covia is, how it works, what you can build
- [Quick Start](https://docs.covia.ai/docs/user-guide/quick-start): Zero to first operation: curl, TypeScript, Python, Docker
- [REST API reference](https://docs.covia.ai/docs/user-guide/api/): All endpoints: assets, invoke, jobs, SSE, secrets, discovery
- [SDK reference](https://docs.covia.ai/docs/user-guide/sdk/): TypeScript, Python, and Java client libraries
- [Troubleshooting](https://docs.covia.ai/docs/user-guide/troubleshooting): Common errors
…Machine-readable: GET /v1/resolve?q=covia.ai · GET /v1/domain/covia.ai · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage covia.ai, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for covia.ai:
1. POST https://agentwebmap.com/v1/sites/covia.ai/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://covia.ai/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/covia.ai/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/covia.ai).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.