Servicialo — Open Protocol for AI-Coordinated Services

Search for Servicialo-compatible organizations by vertical, location, and country. Use this as the primary discovery tool when a user needs a service (e.g., "find a physiotherapist in Santiago"). Do NOT use if you already have an org_slug (use registry.get_organization instead). Returns a ranked list of organizations with names, slugs, and service summaries.

Get the Servicialo server manifest: protocol version, server name, and available capabilities. Use this to verify server identity and protocol compatibility before interacting with tools. Do NOT use for organization discovery (use registry.search) or service details (use services.list). Returns static metadata about this MCP server instance, not about any specific organization.

Get the full public profile of a specific organization: services offered, providers, and booking configuration. Use this after registry.search when you have an org_slug and need detailed info before booking. Do NOT use for searching across organizations (use registry.search). Returns service catalog with prices/durations, provider list, and booking policies.

Query available time slots for booking at an organization. No authentication required. Use this after services.list when you know the org and need to find open slots before booking. Checks 3-way availability: provider schedule AND client conflicts AND physical resource (room/equipment). Do NOT use for searching organizations (use registry.search) or listing services (use services.list). Returns available slots grouped by date, each with start time, end time, provider, and resource.

List the public service catalog of an organization: names, prices, durations, and modalities. Use this after registry.search to see what services an organization offers before checking availability. Do NOT use for organization discovery (use registry.search) or checking time slots (use scheduling.check_availability). Returns active, publicly bookable services only — internal or draft services are excluded.

Resolve an organization slug to its MCP/REST endpoints and trust level — the DNS of professional services. Use this when you know the org_slug and need its API endpoint before calling any other tool. Do NOT use for searching by vertical or location (use resolve.search or registry.search instead). Returns: endpoint URLs, trust score (0-100), trust level, and last heartbeat timestamp.

Search the global Servicialo resolver for registered organizations by country and vertical. Use this for broad discovery when you need to find all organizations in a country/vertical (e.g., "what physiotherapy clinics exist in Chile?"). Do NOT use if you already have an org_slug (use resolve.lookup instead). Unlike registry.search, this queries the DNS-level resolver and returns endpoint URLs + trust levels.

Get the trust score of an organization from the Servicialo resolver. Use this to evaluate reliability before booking — returns score (0-100), trust level (unverified → declared → vouched → verified), and last activity timestamp. Do NOT use this to find organizations (use resolve.search). Trust accumulates passively from verified service history; it cannot be purchased or self-declared.

Get the A2A (Agent-to-Agent) Agent Card for an organization, enabling inter-agent discovery. Use this when your agent needs to communicate with another agent managing this organization — the card declares supported capabilities, endpoints, and authentication requirements. Do NOT use for human-facing discovery (use registry.get_organization) or service listing (use services.list). Returns a JSON-LD Agent Card following the A2A v0.3 specification.

Get the complete 5-step onboarding guide as structured JSON data. Use this when helping a new organization join the Servicialo network — covers installation, signup, credentials, MCP client config, and publishing. Do NOT use for searching services (use registry.search) or checking availability (use scheduling.check_availability). Returns step-by-step instructions, config templates, and links. No parameters required.

List every (event_type, vertical, region) segment that has at least 5 distinct contributing organizations over the last 90 days — i.e. every benchmark that the protocol is allowed to publish without violating k-anonymity. Use this to discover what benchmarks exist before issuing market.get_benchmark. Filters are optional; passing none lists all available segments sorted by contributor count. Returns: array of { event_type, vertical, region, sample_size, contributors, first_event, last_event }.

Get the bucket distribution for a (event_type, vertical, region) segment over a time window. Returns the share of each bucketed value within the payload (e.g. for booking_created, the share of bookings in each lead_time_bucket). All values are categorical buckets — no raw prices, durations, or names are ever returned. If the segment has fewer than 5 distinct contributing organizations, returns { ok: false, reason: "insufficient_data", contributors }. Use market.list_segments first to know which segments will return data. Example: market.get_benchmark({ event_type: "payment_settled", vertical: "health", region: "CL" }) → distribution of price bands, payment methods, time-to-collect buckets.

List every vertical present in the Servicialo network. Combines (a) verticals that registered nodes declare and (b) verticals observed in operational telemetry over the last 30 days. Use as the first call when an agent has no prior knowledge of the protocol taxonomy — before issuing market.get_benchmark, registry.search, or any other call that requires a `vertical` argument. Returns: array of { name, org_count, event_count_30d } sorted by activity. Test fixtures (verticals starting with `_`) are excluded.

List every country/region present in the Servicialo network. Combines countries declared by registered nodes with regions observed in operational telemetry over the last 30 days. Use this when an agent needs to know "where is this protocol active?" before issuing a region-scoped query. Returns: array of { code, org_count, event_count_30d } sorted by activity. Codes are ISO 3166-1 alpha-2.

List the catalog of operational-telemetry event types defined by the Servicialo protocol. Static (changes via RFC), but exposed as a discovery call so agents can know what event names market.get_benchmark accepts and what bucketed fields each event carries — without having to read the JSON Schema. Returns: array of { name, description, payload_fields[] } plus a `schema_url` for the canonical reference.