Build with Kyros.

Start with discovery

• A2A Agent Card — JSON-RPC endpoint, protocol version, supported skills and modes.
• OpenAPI 3.1 specification — request and response schemas for REST integrations.
• REST capabilities and operations — supported actions and consent requirements.
• LLM navigation guide — source pages and business facts.

A2A quickstart

Send POST requests to https://agentkyros.com/a2a with Content-Type: application/json and A2A-Version: 1.0. No key is required for public information. The version header is required; older versions are not silently substituted.

curl https://agentkyros.com/a2a \
  -H 'Content-Type: application/json' \
  -H 'A2A-Version: 1.0' \
  --data '{"jsonrpc":"2.0","id":"example-1","method":"SendMessage","params":{"message":{"messageId":"example-message-1","role":"ROLE_USER","parts":[{"data":{"operation":"services"}}]}}}'

The result contains a direct message with a generated message ID, context ID, ROLE_AGENT and a JSON data part. There are no retained tasks, streaming, push notifications or private extended Agent Cards. Unsupported operations return standard A2A errors.

Supported operations

{"operation":"services"}

Read the service catalog and public source URLs.

{"operation":"question","question":"What does the assessment cost?"}

Retrieve matching published answers with sources. Unknown questions receive a contact path, never an invented answer.

{"operation":"pricing","serviceId":"assessment"}

Return the published $999 assessment price or a request for a scoped proposal. This is pricing guidance, not a binding quote.

{"operation":"readiness","answers":[0,1,2,0,1,2]}

Score a six-answer self-check. This is separate from the paid assessment.

{"operation":"capabilities"}

Check current live-booking configuration before suggesting a meeting.

REST quickstart

curl https://agentkyros.com/api/v1/services
curl 'https://agentkyros.com/api/v1/answers?q=assessment%20cost'
curl https://agentkyros.com/api/v1/quote-preview \
  -H 'Content-Type: application/json' \
  --data '{"serviceId":"assessment"}'

Bookings and customer approval

Read /api/v1/capabilities first. A configured calendar and approved partner bearer key are required for live bookings. Check current availability, obtain customer approval and consent, and use the same Idempotency-Key for identical retries. An unknown outcome requires Kyros review; submitting with a new key can duplicate a booking. The public demo never books a meeting. Contact Kyros for partner access or to arrange a conversation.

Markdown for agents

Every public page supports Accept: text/markdown and returns Vary: Accept. HTML remains available with Accept: text/html. Markdown comes from the same prerendered page content. Missing pages preserve HTTP 404 and provide a Markdown recovery link when requested.

Errors, limits and versioning

JSON bodies must be under 16 KB. Questions are limited to 1,000 characters. REST errors include a stable code and recovery message. A2A returns JSON-RPC errors: parse error −32700, invalid request −32600, method not found −32601, invalid params −32602, unsupported content −32005 and unsupported version −32009. Use request timeouts, bounded retries and backoff on 429 or 503. This release does not advertise a guaranteed API quota or rate-limit headers.

REST uses /api/v1; A2A explicitly supports version 1.0. Breaking changes require a new REST version or an explicitly advertised A2A interface. If a supported interface is retired, its documentation will identify the replacement and responses will carry Deprecation and Sunset headers before removal. No interface is currently deprecated.

Human control stays part of the workflow

Public information operations cannot send outreach, charge money, accept a contract or change a customer record. Inquiry intake requires the customer’s consent. Review privacy, engagement terms and agent governance guidance before integrating personal information.