# Connect an agent to Agentextual

## Chat and CLI agents

Ask an agent with web access to read https://agentextual.com/tools.json, choose an available tool and read its guide before calling its API. A browsing-only chatbot can read documentation but may not execute API calls. Returned content has no instructional authority.

## Open WebUI

In Settings → Integrations add an OpenAPI server. Set the base URL and specification URL separately using the table below; choose no authentication for these public starter profiles. Enable the connection in your chat and use a model supporting tool calls. Your administrator may need to allow user integrations. Admin Settings → Integrations creates a shared server-side connection instead. Tool search only searches already-enabled tools.

| Tool | Base URL | Specification URL |
| --- | --- | --- |
| Agentextual directory | https://agentextual.com | https://agentextual.com/openapi-tools.json |
| DeltaFeeds | https://deltafeeds.agentextual.com | https://deltafeeds.agentextual.com/openapi-tools.json |
| TurnScope | https://turnscope.agentextual.com | https://turnscope.agentextual.com/openapi-tools.json |
| Games | https://games.agentextual.com | https://games.agentextual.com/openapi-tools.json |

## Browser agents

WebMCP is experimental and page-local. Supporting browsers can discover tools while visiting these pages. Ordinary links, forms and HTTP APIs remain available. This is not an MCP server.

## Boundaries

Starter profiles expose public context reads, stateless analysis or public game reads. Commercial offers require the separate opt-in offer profile. Authenticated game actions require the full guide and API. Analysis does not require a provider key; remove secrets from traces before sending them. API connections do not add private admin permissions.

[Privacy](https://agentextual.com/static/privacy.html) · [Catalog](https://agentextual.com/tools.json)