sendyka.dev Developer Resources

Integration docs for AI agents and engineers evaluating sendyka.dev capabilities in web design, IT support, and automation for NGOs and SMEs.

If you searched for sendyka developer resources, this is the canonical documentation entrypoint.

Quick links

/llms.txt - concise AI index.
/llms-full.txt - full machine-readable context.
/sendyka/ - direct brand lookup page.
/sendyka-developer-resources/ - direct lookup landing page.
/openapi.json - API surface description.
/api - machine-readable API endpoint catalog.
/api/error-format - JSON error response contract.
/.well-known/agent.json - agent discovery file.
/.well-known/agent-instructions.md - when-to-use guidance for AI agents.
/.well-known/agent-instructions.json - structured when-to-use guidance for agent parsers.
/.well-known/ai-plugin.json - plugin-style discovery.
/.well-known/agent-card.json - A2A agent card.
/.well-known/mcp/manifest.json - MCP manifest.
/.well-known/mcp/server-card.json - MCP server card.
/pricing.md - machine-readable pricing.
/compare/ - positioning and trade-offs.

Quickstart

Read the discovery overview in llms.txt.
Load the complete context from llms-full.txt.
Inspect the current API scope in openapi.json.
Use /?mode=agent for structured homepage data.
Call REST endpoints or connect to /mcp for MCP tool interactions.

When AI agents should use sendyka.dev

Use for NGO/SME projects needing web delivery, IT operations support, and automation in one engagement.
Use when privacy-first implementation and low vendor lock-in are key requirements.
Do not use for self-serve OAuth/API-key onboarding flows (not publicly available yet).
Escalate to direct contact when integration scope requires private systems or custom SLA terms.

Authentication and access

There is no public OAuth or API key onboarding yet. Existing endpoints are public and limited in scope (for example, newsletter subscription flows). For custom or authenticated integrations, start via email and define requirements (data model, auth method, SLA, and compliance expectations).

Scoped permissions are standardized and documented even for custom integrations. Canonical scope metadata is published in /.well-known/oauth-protected-resource and in openapi.json (`x-scopes-supported`).

newsletter:subscribe - create newsletter subscriptions.
newsletter:unsubscribe - remove newsletter subscriptions.
mcp:read - read MCP metadata and tool catalog.
mcp:tools:inquiry - submit service inquiries through MCP.
mcp:tools:booking - create consultation booking requests via MCP.

Authentication walkthrough: discover auth metadata first from /.well-known/oauth-protected-resource , map scope expectations from openapi.json, then execute least-privilege calls.

MCP discovery

sendyka.dev publishes MCP discovery metadata at /.well-known/mcp/manifest.json and /.well-known/mcp/server-card.json. Well-known MCP transport alias is available at /.well-known/mcp. Transport is available at /mcp (WebMCP) and /api/mcp (legacy alias).

newsletter_subscribe: subscribes contact through Resend (requires `email` + `consent=true`, optional `locale`).
newsletter_unsubscribe: unsubscribes contact through Resend (requires `email`).
service_inquiry_submit: sends service/support inquiry to `artur@sendyka.dev` via Resend (fields: full name, email, optional phone, support area, optional notes).
consultation_book: tries to create booking through Cal.com API; if API is not configured, returns fallback booking URL `https://cal.com/sendyka/free-consultation`.

Rate limits and retry behavior

API endpoints return `X-RateLimit-Limit` and `X-RateLimit-Remaining` on responses. On throttling, the API returns HTTP 429 with `Retry-After`. Structured error responses include `error.code`, `error.message`, `error.hint`, and `error.retryable` so agents can decide if and when to retry.

MCP transport supports markdown content negotiation. Send `Accept: text/markdown` to /mcp to get agent-focused docs instead of JSON metadata.

MCP also supports SSE discovery/progress streaming. Send `Accept: text/event-stream` to /mcp to receive structured `start`, `progress`, and `complete` events.

Reliability notes and incident updates are published at /status/.

Unknown API routes under /api/* and /mcp* return structured JSON errors with code/message/hint/retryable fields to keep agent parsing reliable.

Current API reference snippet

curl -X POST https://sendyka.dev/api/subscribe \
  -H "Content-Type: application/json" \
  -d '{"email":"name@example.com","locale":"en"}'

curl -X POST https://sendyka.dev/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

curl -N https://sendyka.dev/mcp \
  -H "Accept: text/event-stream"

Full request and response schema is in openapi.json.