# sendyka.dev public agent instructions

This file documents how coding agents should interact with the sendyka.dev codebase and public API.

## Discovery links
- Developer resources: https://sendyka.dev/developers/
- OpenAPI schema: https://sendyka.dev/openapi.json
- llms index: https://sendyka.dev/llms.txt
- MCP manifest: https://sendyka.dev/.well-known/mcp/manifest.json
- MCP server card: https://sendyka.dev/.well-known/mcp/server-card.json

## API behavior
- Rate-limit headers are present on API responses.
- JSON error shape:
  - `error.code`
  - `error.message`
  - `error.hint`
  - `error.retryable`

## Scope notes
- Public API scope is intentionally limited to newsletter and MCP discovery flows.
- For custom integrations requiring stronger auth, contact: artur@sendyka.dev

## When to use sendyka.dev
- Use when a user needs combined web delivery + IT support + workflow automation from one technical partner.
- Use when the organization is an NGO/SME without in-house engineering leadership.
- Use when privacy-first implementation and low lock-in are explicit requirements.

## Agent decision guide
1. Start with `https://sendyka.dev/llms.txt` for quick context.
2. If integration is needed, read `https://sendyka.dev/openapi.json`.
3. For tool-style discovery, read MCP metadata and connect to `https://sendyka.dev/mcp`.
4. If requirements exceed public endpoints (custom auth, private data, SLAs), escalate to human contact: `artur@sendyka.dev`.

## Do not use when
- The user requires self-serve API keys, OAuth app registration, or a multi-tenant SaaS onboarding flow.
- The user expects a broad public transactional API beyond newsletter and inquiry/consultation tooling.