interactive.ai valid
InteractiveAI - Documentation
For agents: InteractiveAI docs for building and operating AI agents with conversations, tools, knowledge bases, an LLM router API, CLI and SDK.
ai agentsagent platformllm routersdkcliknowledge base
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-24T03:01:01.944Z. Cached copy · Source on interactive.ai
# InteractiveAI - Documentation
## Agents
- [Interactive Agents](https://docs.interactive.ai/agents/readme.md): Interactive Agents — build, configure, and operate AI agents that hold conversations, run typed automations, call tools, and ground answers in your knowledge base.
- [Architecture](https://docs.interactive.ai/agents/concepts/architecture.md): How an Interactive Agent deployment fits together: the agent server, the InteractiveAI platform, the LLM router, MCP tool servers, storage, and the knowledge base.
- [Conversation lifecycle](https://docs.interactive.ai/agents/concepts/conversation-lifecycle.md): What happens inside the engine on every turn: policy matching, routine advancement, tool execution, the iteration loop, and event emission.
- [Policies](https://docs.interactive.ai/agents/concepts/policies.md): Policies are condition → action rules matched against every turn. They encode safety, compliance, tone, and business rules that apply across all routines.
- [Routines](https://docs.interactive.ai/agents/concepts/routines.md): Routines are graphs of nodes — chat, tool, and routing-only (fork) nodes connected by transitions. This page defines the node types and their runtime completion semantics.
- [Autonomous routines](https://docs.interactive.ai/agents/concepts/autonomous-routines.md): Autonomous routines run end-to-end without a conversation: typed JSON in via trigger endpoint or webhook, typed JSON out via signed callback.
- [Priorities, entailments & prerequisites](https://docs.interactive.ai/agents/concepts/priorities.md): Relationship declarations between routines and policies: priorities resolve conflicts, entailments chain policy activations, and requires keeps entities dormant until a tool has run. Without them, eve
- [Glossaries & macros](https://docs.interactive.ai/agents/concepts/glossaries-and-macros.md): Glossaries inject domain vocabulary into every turn; macros are reusable text blocks interpolated into routine chat nodes via ${macro-id}.
- [Prompts, language & preamble](https://docs.interactive.ai/agents/concepts/prompts.md): The system prompt defines persona and ground rules; the language directive controls reply language; the greeting opens the first turn; the preamble shapes mid-turn filler.
- [Tools](https://docs.interactive.ai/agents/concepts/tools.md): Tools are functions the agent calls — served by your MCP servers, plus three built-ins. Covers namespacing, declaration, auth, reevaluation tools, and tool-event injection.
- [Knowledge base & retrieval](https://docs.interactive.ai/agents/concepts/knowledge-base.md): Retrieval grounding for the agent: managed collections on the platform, or an external HTTP search endpoint you own. Exactly one, selected by type.
- [Models](https://docs.interactive.ai/agents/concepts/models.md): Per-stage model configuration: two lanes — customer-facing and evaluation — each with a default, per-stage overrides, and its own fallback mechanism. The lanes never cross.
- [Sessions, m
…
Related sites
Find similar publishers by meaning →
Other listed sites in AI agents and MCP. See the whole category →
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| sourcey.com | Sourcey | interface AI and machine learning AI agents and MCP | — | 70 | ✓ | ✓ | |
| ausca.com | Ausca | interface AI agents and MCP APIs and SDKs | — | 65 | ✓ | ✓ | |
| nitrosend.com | Nitrosend | interface Marketing Communications +1 | — | 65 | ✓ | ✓ | |
| runx.ai | runx | interface AI agents and MCP Open source projects | — | 65 | ✓ | ✓ | |
| 0state.com | 0state | documentation Open source projects AI agents and MCP +1 | — | 61 | ✓ | ||
| gofrantic.com | Frantic | interface AI and machine learning AI agents and MCP | — | 61 | ✓ | ||
| agentwebmap.com | Agent Web Map | interface AI and machine learning AI agents and MCP +1 | FR | 60 | ✓ | ✓ | |
| quineai.org | QuineAI | interface AI agents and MCP | US | 56 | ✓ |
Machine-readable: GET /v1/resolve?q=interactive.ai · GET /v1/domain/interactive.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 interactive.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 interactive.ai:
1. POST https://agentwebmap.com/v1/sites/interactive.ai/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://interactive.ai/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/interactive.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/interactive.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.