# re:solved

> re:solved builds and deploys custom AI agents that take over manual, repetitive work in growing businesses. We identify where a business is losing time and money, then configure a tailored AI agent around that specific problem — integrated with tools the team already uses. Every deployment includes ongoing monthly management: monitoring, maintenance, and continuous improvement. A fully self-hosted option is available for industries where data must stay on-premise (healthcare, legal, finance).

## Public pages

- [Homepage](https://re-solved.digital/) — Overview of the service, process, use cases, pricing plans, FAQ, and contact.
- [Blog](https://re-solved.digital/blog) — Articles about AI agents, operational automation, and what works for small and mid-sized businesses.
- [AI automation services](https://re-solved.digital/ai-automation-services) — Managed roles, scope and pricing.
- [ROI calculator](https://re-solved.digital/roi-calculator) — Estimate payback for a managed role.
- [About](https://re-solved.digital/about) — Company and founder details.
- [Contact](https://re-solved.digital/contact) — Email contact@re-solved.digital, phone +40 745 071 490, registered office in Timișoara, Romania; response times and languages.
- [Software Services Are Dead. Long Live AI Agents.](https://re-solved.digital/blog/software-services-are-dead)
- [Your team already uses WhatsApp. Your AI agent should be there too.](https://re-solved.digital/blog/whatsapp-ai-agents)
- [What to Look For in an AI Automation Agency (+ Red Flags)](https://re-solved.digital/blog/how-to-choose-ai-automation-agency)
- [AI Agent Examples: What They Actually Do for a Small Business](https://re-solved.digital/blog/ai-agent-examples)
- [What an AI agent actually is — explained for business owners, not engineers](https://re-solved.digital/blog/what-is-an-ai-agent)
- [AI agents vs. chatbots: the difference between answering and acting](https://re-solved.digital/blog/ai-agents-vs-chatbots)
- [Is it safe to give your customer data to an AI? GDPR and automation, explained](https://re-solved.digital/blog/is-it-safe-to-give-ai-your-customer-data)
- [Make.com vs Zapier for AI Agents: Which Platform Builds Autonomous Workflows?](https://re-solved.digital/blog/make-vs-zapier-ai-agents)
- [AI Automation for Healthcare: HIPAA, GDPR, and the Self-Hosted Option](https://re-solved.digital/blog/ai-automation-for-healthcare)
- [AI agents vs. virtual assistants: which one should you hire for repetitive work?](https://re-solved.digital/blog/ai-agents-vs-virtual-assistants)
- [AI Automation for Law Firms: Legal AI Agents That Keep Client Files On-Premise](https://re-solved.digital/blog/ai-automation-for-law-firms)
- [Two rules, both correct: what the EU AI Act actually asks of a business using an AI assistant](https://re-solved.digital/blog/eu-ai-act-what-it-asks-of-your-business)

## Developer resources

- [re:solved developer docs](https://re-solved.digital/developers) — re:solved developer portal: API endpoints, authentication, JSON error format, rate limits, versioning and MCP server. Aliases: https://re-solved.digital/docs, https://re-solved.digital/api-docs, https://re-solved.digital/mcp-server (all canonicalise to https://re-solved.digital/developers).
- [re:solved API docs](https://re-solved.digital/api-docs) — Named entry point for the re:solved API documentation (endpoints, schemas, errors, rate limits).
- [re:solved MCP server docs](https://re-solved.digital/mcp-server) — Named entry point for the re:solved MCP server documentation (transport, tools, manifest).
- [re:solved authentication docs](https://re-solved.digital/developers#authentication) — Credentials policy: public HTTP endpoints and the MCP server require no API key and no signup.
- [re:solved OpenAPI specification](https://re-solved.digital/openapi.json) — OpenAPI 3.1 document describing every public endpoint (alias: https://re-solved.digital/api/openapi.json).
- [re:solved MCP server](https://re-solved.digital/mcp) — Model Context Protocol endpoint with tools: get_services_and_pricing, list_blog_posts, search_blog_posts, get_blog_post. Streamable HTTP transport, no authentication required; manifest at https://re-solved.digital/.well-known/mcp.json.
- [re:solved services & pricing API](https://re-solved.digital/api/public/v1/services) — GET JSON: positioning, managed roles, delivery process, pricing plans, FAQ. No key, no signup (?language=en|ro).
- [re:solved blog content API](https://re-solved.digital/api/public/v1/blog/posts) — GET JSON list/search of guides (?q=, ?limit=, ?language=), full markdown at https://re-solved.digital/api/public/v1/blog/posts/{slug}. No key, no signup.
- [re:solved API onboarding](https://re-solved.digital/developers#zero-auth) — Zero-auth free tier: no API key, no account, no contact-sales step. Sandbox: POST "dry_run": true to https://re-solved.digital/api/public/v1/ai-audit-submit to validate a submission without creating a lead. Machine-readable: x-agent-onboarding in https://re-solved.digital/openapi.json.
- [re:solved AI audit intake API v1](https://re-solved.digital/api/public/v1/ai-audit-submit) — POST JSON to request an AI Automation Opportunity Report (unversioned alias: https://re-solved.digital/api/public/ai-audit-submit).
- [re:solved API versioning & deprecation policy](https://re-solved.digital/api/public/versions) — URL path versioning (/api/public/v1/...), API-Version header, Deprecation/Sunset headers with 180 days notice. Human version: https://re-solved.digital/developers#versioning.
- [re:solved API rate limits](https://re-solved.digital/developers#rate-limits) — 60 requests / 60 seconds per IP; IETF RateLimit + RateLimit-Policy headers on every API response, Retry-After on 429 (code: rate_limited). Machine-readable: https://re-solved.digital/api/public/versions.
- [re:solved API deprecation & sunset policy](https://re-solved.digital/deprecation-policy) — What counts as breaking, Deprecation/Sunset (RFC 8594) headers, minimum 180 days notice, HTTP 410 after sunset.
- [re:solved API catalog](https://re-solved.digital/.well-known/api-catalog) — RFC 9727 linkset for the API surface.

## Machine-readable files

- [sitemap.xml](https://re-solved.digital/sitemap.xml)
- [ai.txt](https://re-solved.digital/.well-known/ai.txt)
- [rss.xml](https://re-solved.digital/rss.xml)

## Notes

- Romanian versions of pages live under the /ro prefix.
- Unknown paths return HTTP 404 with a short markdown body listing these resources.
- All /api/* errors are JSON: { error: { code, message, hint, status, docs, openapi } }.