Product
One answer. Your way in.
Every surface hits the same router, spends the same credits, and returns the same envelope: one request in, one verified answer out. Pick by where you work, not by feature — there is only one feature, and everything has it.
HTTP API
Your backend, scripts, Salesforce Flow, Zapier, or anything that can POST.
Bearer key · api.kingminos.com
MCP server
Cursor, Claude, or any MCP client. One tool per route, same answers.
Streamable HTTP · mcp.kingminos.com
CLI
Your terminal. One command per route, JSON out.
npx kingminos
Agent Skills
Coding agents that follow skill workflows.
npx skills add outboundsync/kingminos-skills
For machines reading this page
- OpenAPI 3.1 — The machine-readable contract. Same file at /openapi.yaml and /v1/openapi.yaml.
- Try it live — Run any route from the docs. The health check needs no key.
- llms.txt — What KingMinos is, and every surface, in plain text for agents.
- This site, for agents — MCP and content negotiation on kingminos.com itself: markdown mirrors, remote MCP.
Bring your own vendor keys
KingMinos runs the waterfall across vendors. Some run on house keys; the paid ones — ZoomInfo, Apollo, Clay, Cognism, Lusha, and the rest — run on the keys you store. A step that runs on your own vendor key costs 0.1 KingMinos credits, so those answers barely touch your balance. Pay as you go is $0.10 per credit if you would rather not commit to a plan.