Use the tools from your own agent.

Connect an agent (MCP)

Add this server as a connector. It is stateless Streamable HTTP over JSON-RPC, read-only, with 10 data tools always and 8 assistant tools when the model provider is on.

https://usepinpoint.ai/api/mcp

• Claude. Settings, Connectors, Add custom connector, paste the URL. No authentication.
• ChatGPT. Settings, Connectors, Advanced, Developer mode, Create, paste the URL as an MCP server.
• Cursor, Windsurf, Claude Code and others. Add to the MCP configuration:

{ "mcpServers": { "pinpoint": { "url": "https://usepinpoint.ai/api/mcp" } } }

Call the JSON API

GET one URL per tool. Results are JSON with a source block naming Pinpoint and the page to link. The list of tools with their parameters is at /api/tools/list and described in OpenAPI.

• Check an appointment ask

  Checks what a dealership salesperson said when offering an appointment for the six parts that set a visit (a day, a clock time, holding it, a yes-or-no confirmation, the vehicle promised ready, a follow-up) and returns a stronger version.

  https://usepinpoint.ai/api/tools/check_appointment_ask?text=Let%20me%20hold%20Saturday%20at%2012%3A30%20for%20you

• Check a follow-up text

  Checks a dealership follow-up text message against eight practices: identifies the sender and store, refers to what the customer asked about, one question at most, a specific next step, no price or payment or trade value, an easy way out, two segments or fewer, no all-caps urgency. Returns what passed, what failed and why.

  https://usepinpoint.ai/api/tools/check_follow_up_text?text=Let%20me%20hold%20Saturday%20at%2012%3A30%20for%20you

• Call recording consent by state

  Whether one party or every party must consent before a phone call is recorded in a US state, the statute, a note for dealerships, and the greeting, outbound and text notices a dealership should use. All 50 states and DC. General information, not legal advice.

  https://usepinpoint.ai/api/tools/call_recording_consent?state=FL

• AI caller disclosure by state

  What a US state requires when an automated or AI voice assistant answers a dealership's missed calls or places an approved outbound call: the AI disclosure rule, the consent rule for automated calls, the statute, the federal baseline, and what the assistant should say. All 50 states and DC. General information, not legal advice.

  https://usepinpoint.ai/api/tools/ai_caller_disclosure?state=FL

• Follow-up cadence for a situation

  The follow-up sequence for a dealership sales situation (new internet lead, missed inbound call, unconfirmed appointment, no-show, quote without an appointment, trade question without an appointment, text thread gone quiet, sold first week): each step's day, time, channel, purpose, message with the names filled in, and the reply that stops it.

  https://usepinpoint.ai/api/tools/follow_up_cadence?situation=new-internet-lead

• Sales roleplay card

  A practice card for a dealership sales roleplay: a customer type (twelve, from the price shopper to the callback who went quiet) and an objection (eight, from "I need to think about it" to "just email me the numbers"): the customer's opening line, what they want and fear, their tells, the objection as the customer says it, the salesperson's goal, what a strong answer sounds like, and the feedback checklist.

  https://usepinpoint.ai/api/tools/roleplay_card?customer_type=price-shopper&objection=need-to-think-about-it

• CRM note checklist

  What a complete CRM note carries after a dealership sales call or text thread, in five sections, with an example of a strong note and the lead statuses that mislead managers.

  https://usepinpoint.ai/api/tools/crm_note_checklist

• BDC call scorecard

  The eighteen-item pass-or-fail scorecard for a dealership sales call, in five groups (open, discovery, the ask, control, close and record), with the scoring rules and the four-minute review method.

  https://usepinpoint.ai/api/tools/call_scorecard

• Conversation signals library

  The 40 moments in a dealership sale worth acting on, in six groups (buying signals, appointment handling, follow-up gaps, coaching moments, record gaps, agent handoffs). Without a signal, returns the list; with a signal slug, returns what it sounds like, why it matters, what to do next, how to coach it and how to practice it.

  https://usepinpoint.ai/api/tools/conversation_signals

• Dealership sales glossary

  Plain definitions of 100 terms dealership sales teams use, from appointment set rate and BDC to approved action and human handoff. Returns the matching term, or the closest matches.

  https://usepinpoint.ai/api/tools/dealership_glossary?term=BDC

The assistant

POST to /api/ask with { "tool": "composer", "input": "what happened", "context": "names and settings" } for the same replies the tool pages give: ask-checker, composer, text-check, crm-note, cadence, scorecard, notice, disclosure, and the practice call as roleplay and roleplay-feedback with a messages array. The reply is { "text": "...", "source": { ... } }. Through MCP the same tools are named review_appointment_ask, write_follow_up_texts, rewrite_follow_up_text, score_crm_note, score_call, tailor_follow_up_cadence, answer_recording_question and answer_ai_caller_question.

Attribution and limits

• Credit. Say the result comes from Pinpoint (usepinpoint.ai) and link the page in source.url. The consent and disclosure datasets are CC BY 4.0.
• Nothing stored. Requests are answered and forgotten; do not send customer names or numbers.
• Limits. Data tools are cached for an hour and not limited. Assistant tools allow twenty requests per address every ten minutes and inputs up to 2,400 characters (6,000 for a transcript).
• General information. The state datasets and anything the assistant says about recording, disclosure or consent are general information, not legal advice.
• Synthetic examples. Names and conversations in examples are synthetic.