# Connect an agent

## Obtain the endpoint

The supplied 2026-10-01 captures use `https://dev.testril.ai/mcp`, with Base Sepolia testnet USDC for payments. See the [captured Workflow examples](/agents/workflow-examples.md). This identifies the recorded service; confirm the intended deployment and access requirements with the operator before integration. `<MCP_URL>` in generic examples is a placeholder; do not infer an endpoint from the website domain.

The implementation exposes an HTTP MCP route at `/mcp`. A self-hosted daemon's documented local default is `http://127.0.0.1:8000/mcp`. This loopback URL refers to your own machine, not the hosted Testril service.

## Discover the live contract

Use your MCP client's connection lifecycle, then request `tools/list`. Save the advertised tool names, input schemas, output schemas, and server instructions. The implementation supports the legacy initialize lifecycle as well as a stateless protocol generation; let a compatible client negotiate its supported version instead of guessing transport metadata.

The expected public tools are `health_check`, `inspect`, `bind`, `ask`, `materialize`, `pay_quote`, `read`, `provenance`, `stop`, and `claim_rewards`. `quote` is an internal retired entry point; request prices through `materialize` or `read`. Administrative operations are outside this public reference; do not infer access from the public MCP endpoint.

If the deployed list differs, use the deployed schemas and report the mismatch to the operator. Do not call an unadvertised tool.

The release review on 2026-10-07 connected to the recorded development endpoint, which reported version `0.6.0`, and confirmed these 10 tool names and their documented input-field inventory through `tools/list`. That read-only check does not establish mainnet payment support or end-to-end metric execution. Live instructions also advertise declared bindings and dependency-aware materialization beyond the reviewed local revision. Live schemas still contain unsigned formats such as `uint64` that the reviewed local implementation removes; account for schema-validator warnings until that change is deployed. See the [release review](/agents/).

## First calls

```json
{"tool":"health_check","arguments":{}}
```

```json
{"tool":"inspect","arguments":{"subject":"chains"}}
```

```json
{"tool":"inspect","arguments":{"subject":"functions"}}
```

The `{tool, arguments}` objects throughout this reference are **documentation notation**, not raw MCP transport messages. Invoke the named tool with those arguments through your client. Chain support is deployment-specific: a marketing coverage number does not establish which RPC providers a particular server has configured.

## Optional REST discovery

The daemon also serves a read-oriented `/v1` API and an OpenAPI document at `/v1/openapi.json`. Use the service's advertised origin and the `data_endpoints` returned by tools when present. Do not construct routes from the homepage demo. Authoring and other writes stay on MCP.

## Record an integration fingerprint

Store the endpoint, negotiated protocol version, discovered tool schemas, configured chain IDs, and the time of discovery. Recheck after server upgrades. Keep authentication and RPC credentials outside logs and prompts; inspect and provenance data should be sufficient without exposing a provider's secret URL.