openvibe.actor valid

OpenVibe.Actor

OpenVibe.Actor: an AI agent router and OpenVibe's own agent. A task in plain words goes to the best agent system for it, by what the task needs and the caller's mode (cheapest, balanced, best, fastest, private); a second model family checks the answer; the task records its cost to a fraction of a cent and why that agent was picked.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-22T15:47:19.836Z. Cached copy · Source on openvibe.actor

# OpenVibe.Actor

> OpenVibe.Actor: an AI agent router and OpenVibe's own agent. A task in plain words goes to the best agent system for it, by what the task needs and the caller's mode (cheapest, balanced, best, fastest, private); a second model family checks the answer; the task records its cost to a fraction of a cent and why that agent was picked.

Agents today: the OpenVibe runtime (a DeepSeek model acting through OpenVibe.Search and OpenVibe.Tools: DNS, mail records, certificates, headers, WHOIS and more), OpenAI's web agent (live web search with sources), and an open model on OpenVibe's own server for private mode. Coding goes to OpenVibe.Codes. Every page is server-rendered and readable without JavaScript. The API: POST /api/v1/tasks, GET /api/v1/tasks/:id, GET /api/v1/tasks/:id/events (server-sent events), POST /api/v1/tasks/:id/cancel, GET /api/v1/agents and POST /api/v1/route (public dry run). Tasks are platform.task@1 in openvibe-contracts.

## Start here

- [Give Actor a task](https://openvibe.actor/): what Actor is, how a task finds its agent, what works today
- [The agents](https://openvibe.actor/agents): every agent system with its price, trust class and availability; the modes; the check
- [The API](https://openvibe.actor/docs): tasks, the live stream, errors, limits
- [What shipped on OpenVibe.Actor](https://openvibe.actor/updates)

## Machine-readable

- [The agents (JSON)](https://openvibe.actor/api/v1/agents): actor.agent-list-result@1
- [Dry-run the router](https://openvibe.actor/api/v1/route): POST { task, mode? } → which agent and why (platform.placement-result@1)
- [The free tier (JSON)](https://openvibe.actor/limits.json)
- [Sitemap](https://openvibe.actor/sitemap.xml)
- [Full text for language models](https://openvibe.actor/llms-full.txt)
- [Release metadata (JSON)](https://openvibe.actor/release.json)

## Elsewhere

- [OpenVibe.Codes](https://openvibe.codes): the coding-agent harness Actor sends coding work to
- [OpenVibe.Tools](https://openvibe.tools): the tools the OpenVibe runtime uses
- [OpenVibe.Services](https://openvibe.services): apps, keys and actor.task.* grants

Related sites

Other listed sites in AI and machine learning. See the whole category →

Machine-readable: GET /v1/resolve?q=openvibe.actor · GET /v1/domain/openvibe.actor · 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.

Claim my listing on Agent Web Map for openvibe.actor:
1. POST https://agentwebmap.com/v1/sites/openvibe.actor/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://openvibe.actor/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/openvibe.actor/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/openvibe.actor).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.