Answering Service Care for developers and agents

Answering Service Care (ASC) is a 24/7 US-based answering service with live and AI receptionists. This page lists every way software and AI agents can work with ASC: a public read-only API, the authenticated customer API, an MCP server, and machine-readable versions of the site.

Public API

Base URL: https://answeringservicecare.com/api/v1. No API key or account is needed; every operation is read-only and returns JSON. The full contract, with operation IDs and response schemas, is in the OpenAPI 3.1 document.

Quickstart

curl https://answeringservicecare.com/api/v1/pricing
curl "https://answeringservicecare.com/api/v1/search?q=medical+answering+service&limit=5"

Errors

Errors are JSON with an HTTP status, a machine-readable code, a message, a hint explaining how to fix the request, and a documentation_url. For example, an unknown path returns 404 with "code": "rest_no_route".

Batch requests and async jobs

POST https://answeringservicecare.com/api/v1/batch runs up to 10 of the GET operations above in one request and returns each one's status and body. Each operation counts toward the rate limit. Add Prefer: respond-async to get 202 Accepted with a Location header instead; fetch that job URL (valid for 24 hours) for the results. An Idempotency-Key header is echoed back so you can match responses to requests; because the API changes nothing, repeating a request is always safe.

curl -X POST https://answeringservicecare.com/api/v1/batch \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: 5f1c9a0e-quote-42" \
  -d '{"requests":[{"id":"prices","method":"GET","path":"/pricing","query":{"billingCycle":"monthly"}},{"id":"company","method":"GET","path":"/company"}]}'

Sandbox

https://answeringservicecare.com/api/sandbox/v1 serves the same endpoints, including /batch, with fixed test data that never changes, so tests and demos don't depend on live prices. Sandbox responses include "sandbox": true. The OpenAPI document lists it as a second server.

Customer API

Existing ASC customers can read their messages, call recordings, and to-dos, and connect Zapier or external dispatching, through the customer REST API. Credentials are issued to customers. See the API reference.

MCP servers

The public Model Context Protocol server at https://answeringservicecare.com/mcp needs no account or key. Connect any MCP client over Streamable HTTP to get the public API's data as read-only tools: get_company_info, list_services, get_pricing, search_site, and read_page. The server card lists each tool's inputs, and the server is listed in the official MCP Registry as com.answeringservicecare/public.

Existing customers can also connect to their account through the server at https://mcp.answeringservicecare.com/api/v2/mcp. It is protected with OAuth 2.0; its tools are listed after authorization. The authentication guide walks through discovery and sign-in, and the account server card describes it.

The documentation, including the customer API reference, has its own read-only MCP server at https://answeringservicecare.com/docs/~gitbook/mcp, with the tools searchDocumentation, getPage, and askQuestion. It needs no key; its server card lists the inputs.

Agent skills and plugin

The Answering-Service-Care/agent-skills repository on GitHub packages ASC's two agent skills (researching ASC, and estimating plan cost for a call volume) as an Agent Plugin, together with the MCP server configuration. Install the skills in Claude Code, Codex, Cursor, and other agents with:

npx skills add Answering-Service-Care/agent-skills

SDKs and CLI

Official clients for the public API, with no dependencies, are published as answeringservicecare on npm (JavaScript and TypeScript) and PyPI (Python). Both include an answeringservicecare command that prints JSON. Source: Answering-Service-Care/sdk.

npm install answeringservicecare
pip install answeringservicecare
npx answeringservicecare pricing --service "answering service" --billing monthly

Limits, pagination, and versioning

The public API allows 60 requests per minute per client. Every response carries RateLimit-Policy and RateLimit headers (plus X-RateLimit-*); over the limit you get a JSON 429 with Retry-After. Search is cursor-paginated: pass a response's nextCursor back as cursor.

The major version is in the path (/api/v1). Changes within v1 only add endpoints, fields, and optional parameters. A breaking change ships as /api/v2, and v1 keeps working for at least 12 months after that, with Deprecation and Sunset headers on its responses and a notice on this page.

Machine-readable files

Starting service

There is no sign-up API: a person chooses a plan on the pricing page or talks to sales on the contact page. For questions about integrations, contact ASC there as well.