Sally Skills

Sally Skills

Plug Sally AI into your agent. The clinical-grade health intelligence behind A1C Insights, Sally AI, now exposed as an MCP endpoint and REST API to your agent — 64+ biomarkers across Western clinical and TCM preventive frameworks. Authenticate, call the skills you need, get billed per request. Built for agents who care about health and evidence.

Category
Visit Server

README

Sally Skills

Plug Sally's metabolic-health intelligence into your AI agent. Six skills, per-call pricing, one MCP server. Works with Claude Code, Claude Desktop, Cursor, OpenClaw, Hermes, Manus, Perplexity, or any tool that speaks REST.

Section 1. Onboarding

Before your agent can call any Sally skill, you (the human) need an A1C account and an API key. Two steps.

Step 1. Install A1C Insights and create your account

  1. Open the App Store on your iPhone.
  2. Search for A1C Insights and install it, or open https://apps.apple.com/id/app/a1c-insights/id6748399956 on your phone.
  3. Open the app and tap Sign Up. You can use Sign in with Apple or email + password.
  4. Walk through onboarding (your basics, goals, optional wearables). This creates your A1C user account. Every skill key is bound to one A1C account.

<p align="center"> <img src="assets/onboarding-sync.jpg" alt="A1C Insights syncing your wearable data on first open" width="320" />   <img src="assets/onboarding-home.jpg" alt="A1C Insights home dashboard after first sync" width="320" /> </p>

Visual walkthrough with annotated screenshots: https://console.a1c.io/docs.html#quickstart.

Why iOS first? Skills like metabolic_overview, health_insights, and health_sync read CGM and wearable data the iPhone app collects via HealthKit. You can still use chat_with_sally, analyze_lab_result, and food_journal without any wearable data, but the account itself is created on the iOS app.

Step 2. Mint your API key on console.a1c.io

  1. Visit https://console.a1c.io in any browser.
  2. Sign in with the same A1C account you created in step 1.
  3. Open API Keys, click Create new key, name it (e.g. "Claude Code on my laptop"), and click Generate.
  4. Copy the key now. It starts with sk-sally-… and is shown only once. If you lose it, revoke and re-issue.

You can mint multiple keys per A1C account, one per agent or device, and they all share the same wallet balance. Per-key usage stays auditable.

That's section 1 done. You now have:

  • An A1C account linked to your iPhone app data.
  • A funded wallet.
  • An sk-sally-… API key on your clipboard.

Section 2. Use your key from any agent

You have one key. Three ways to call Sally with it. Most agents only need the MCP path. Pick that unless you're scripting from the command line.

2a. The skill catalog

These six skills go live the moment your key works:

Skill Cost / call What it does Detail
health_sync FREE Pull your wearable, CGM, sleep, vitals, activity, and environment data. 64 fields
chat_with_sally $0.003 Talk to Sally about preventive health and TCM with source citations. usage
analyze_lab_result $0.008 Upload a lab PDF or image; get parsed biomarkers + clinical reading. usage
food_journal $0.004 Snap a photo of your meal; get macros and smart/trap categorisation. usage
health_insights $0.003 Morning, afternoon, or evening readout from your last day of data. usage
metabolic_overview $0.005 CGM snapshot for a date: TIR, variability, spikes, and a narrative. usage

See catalog/ for the full per-skill data breakdown.

2b. Three ways to call

Path Best for Setup
MCP Any modern AI agent (Claude, Cursor, OpenClaw, Hermes, Manus, Perplexity, others). One JSON config block, restart agent, tools appear automatically.
REST API Bash scripts, your own apps, anything that can curl. One HTTP POST per call.
Per-skill REST Same as REST, slightly cleaner URL per skill. /v1/skills/<name>

See protocols/mcp.md for the universal MCP setup, protocols/api.md for raw REST calls, and agents/ for per-agent quick-starts.

2c. Auto-routing for agents and CLIs

Want your agent to pick the right Sally skill for any request without you having to think about it? Drop SKILL.md into the agent's system prompt or instructions field. It's a single file with deterministic routing rules, decision tables, chaining patterns, and anti-patterns. Works with any LLM-based agent or rule-based CLI.

See SKILL.md for the full agent decision layer.

2d. The 30-second smoke test

Confirm your key works before configuring any agent:

curl -sS https://sally.a1c.io/v1/call \
  -H "Authorization: Bearer sk-sally-…" \
  -H "Content-Type: application/json" \
  -d '{"skill":"health_sync","input":{}}' | jq .ok
# → true

true means your key is live and can call the free health_sync skill. You're ready.

Per-agent guides

Pick the agent you actually use:

Don't see your agent? Most modern agents support MCP. See protocols/mcp.md and use the universal config.

Pricing and wallet

  • Per-call pricing, no subscription. See the table above. health_sync is permanently free.
  • Wallet check is enforced before any call. Paid skills return 402 payment_required if your balance is below the price, so there are no surprise charges.
  • Top up via Stripe at https://console.a1c.io/billing. Card payments in USD.
  • Every call writes an immutable row to your usage history. See it in console.a1c.io under Usage.

Privacy and security

  • Your key is your identity. Sally never accepts user_uuid, email, or any other identifier from your agent's request body, only the Authorization: Bearer sk-sally-… header. No agent can impersonate another user.
  • Lab PDFs and meal photos are never persisted by Sally. They flow agent → gateway → AI service → response, with no S3 or GCS upload.
  • Output schemas are allowlists. Sally's response only ever contains the fields explicitly named in each skill's docs. No accidental column leak from internal databases.
  • Revoke instantly at console.a1c.io under API Keys → Revoke. The old key becomes invalid on its next request.

Help

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured