Agentic / integrations

Tools your agent can call.

Use public MCP tools, browser page tools, a testing agent, or signed capabilities. All four connect to a focused set of profile and recovery tools.

Public MCP server

Connect a Streamable HTTP client to https://ruagentic.org/mcp. No credential is required for these read-only tools.

{
  "mcpServers": {
    "agentic": {
      "url": "https://ruagentic.org/mcp"
    }
  }
}

Host configuration formats vary. Select a remote HTTP MCP server when your host provides a setup screen.

  • get_agentic_spec reads the experimental draft.
  • generate_agentic_profile creates a ticket-contract starter.
  • validate_agentic_profile checks supplied JSON and OpenAPI bindings.
  • audit_agentic_url reads public HTTPS files without executing actions.

WebMCP page tools

The generator, validator, and browser lab register tools when the browser supports document.modelContext. Regular controls work in other browsers. The browser lab is a simulation; the hosted platform uses HTTP and PostgreSQL.

A2A testing agent

The agent accepts recovery tests and read-only URL audits, then saves a JSON artifact under a persistent task ID. Create a private session token in the platform first.

AgentCard: https://ruagentic.org/.well-known/agent-card.json
Endpoint:  https://ruagentic.org/a2a
Binding:   JSON-RPC · A2A 1.0
Headers:   Authorization: Bearer <your-session-token>
           A2A-Version: 1.0
           Content-Type: application/json

{
  "jsonrpc": "2.0", "id": "test-1", "method": "SendMessage",
  "params": {
    "message": {
      "messageId": "a-unique-message-id", "role": "ROLE_USER",
      "parts": [{"data": {"kind": "recovery", "scenario": "response-lost"}}]
    }
  }
}

Use GetTask with the returned task ID to retrieve its persisted result. These bounded tests do not offer streaming, push notifications, or cancellation after dispatch.

Agent Auth provider

Register an autonomous agent with the official client. The provider grants only profile validation and isolated synthetic recovery testing. Agents receive a one-hour grant and have a one-day maximum lifetime.

import { AgentAuthClient, MemoryStorage } from '@auth/agent';

const client = new AgentAuthClient({
  storage: new MemoryStorage(), urls: ['https://ruagentic.org']
});
const connection = await client.connectAgent({
  provider: 'https://ruagentic.org',
  mode: 'autonomous',
  capabilities: ['agentic.sandbox.run'],
  name: 'My recovery pilot'
});
try {
  const report = await client.executeCapability({
    agentId: connection.agentId,
    capability: 'agentic.sandbox.run',
    arguments: { scenario: 'response-lost' }
  });
  console.log(report);
} finally {
  await client.disconnectAgent(connection.agentId);
}

Discovery lives at /.well-known/agent-configuration. The implementation uses the official Better Auth plugin, verifies signed requests, and stores grants and replay protection in PostgreSQL. Human account delegation and payments are outside this sandbox.

Install the adoption tools

Download the CLI tarball from the GitHub releases. Install it with Node 24, then initialize or validate a profile.

npm install -g ./ruagentic-0.1.0-draft.3.tgz
agentic init --origin https://your-service.example
agentic validate agentic.json openapi.json

The repository includes a reusable GitHub Action and an adoption skill.

- uses: sam1siam/agentic@v0.1.0-draft.3
  with:
    profile: agentic.json
    openapi: openapi.json
The profile, tools, and test reports are experimental. Project-authored results do not establish independent adoption or certify another service.