Developer Documentation

DEVELOPERS

Agent Discovery & APIs

Machine-readable interfaces for AI agents and developers

Proticom publishes structured discovery documents, an OpenAPI specification, Model Context Protocol endpoints, and agent skills for programmatic access to site knowledge and contact flows.

DISCOVERY SURFACES

llms.txt

Canonical site index for AI crawlers. Short format with approved facts, contact, and primary sections.

/llms.txt →

llms-full.txt

Extended site context with detailed service, product, and industry descriptions for agents that need comprehensive grounding.

/llms-full.txt →

OpenAPI Spec

OpenAPI 3.1 specification documenting public HTTP endpoints (health, MCP, agent registration, contact intake).

/openapi.json →

API Catalog

RFC 9264 linkset documenting service-desc, service-doc, and status relationships for API discovery.

/.well-known/api-catalog →

MODEL CONTEXT PROTOCOL

MCP Streamable HTTP Endpoint

Public MCP endpoint advertising structured discovery tools for site knowledge, services, products, and contact paths. Public tools do not require authentication.

Endpoint: https://proticom.ai/api/mcp

Server card: /.well-known/mcp/server-card.json →

Agent Skills

Skill definitions for engaging Proticom and connecting to the MCP endpoint. Follow the AgentSkills.io 0.2.0 format.

/.well-known/agent-skills/index.json →

engage-proticom skill →

site-mcp skill →

AUTHENTICATION

Agent Registration

Agents can register on behalf of a human via verified email (human_required completion). Public discovery tools and read-only MCP endpoints do not require registration.

Auth documentation: /auth.md →

OAuth metadata: authorization server · protected resource

HTTP API ENDPOINTS

GET /api/health

Health check endpoint. Returns service status and version.

POST /api/mcp

MCP streamable HTTP JSON-RPC endpoint for structured site discovery tools.

POST /api/agent/register

Start verified-email agent registration (human_required completion).

POST /api/contact

Human contact and support intake (Turnstile-protected).

Versioning & deprecation: Current endpoints are stable. Breaking changes will be versioned via URL path (e.g., /v2/) or communicated via Sunset/Deprecation headers with at least 6 months notice.

Rate limits: Public endpoints use IP-based rate limiting (detailed in OpenAPI). 429 responses include RateLimit-* and Retry-After headers.

For human support or questions about these APIs, reach us at contact@proticom.com or /contact.