Simple pricing for every builder
Choose a plan that fits your workflow and scale when your product grows.
Essential
Best for solopreneurs and side projects testing their first app idea with speed.
500 monthly generation credits
Unlimited public projects
Standard AI models
GitHub code export
Community forum support
Free subdomain hosting
Growth
Ideal for scaling startups needing more generations and higher complexity.
Popular
Unlimited generation credits
Premium model access
Unlimited private projects
Custom domain support
Priority email support
Fast processing queue
Integrated database storage
Essential
Best for solopreneurs and side projects testing their first app idea with speed.
500 monthly generation credits
Unlimited public projects
Standard AI models
GitHub code export
Community forum support
Free subdomain hosting
Growth
Ideal for scaling startups needing more generations and higher complexity.
Popular
Unlimited generation credits
Premium model access
Unlimited private projects
Custom domain support
Priority email support
Fast processing queue
Integrated database storage
Frequently asked questions
What is Hunter-Seeker?
Hunter-Seeker is a decision layer your AI agents call over MCP. It ranks a table by the likelihood of a yes/no outcome, scores single entities into act, escalate, or refuse, and signs every decision as an Ed25519 Verdict. The engine is deterministic — the same input produces the same output, byte for byte.
How is this different from letting the LLM decide?
An LLM authors a plausible-sounding number; Hunter-Seeker computes a calibrated one. Agents may generate copy — they may not invent the score. The engine validates on held-out data, refuses when the signal is too weak, and returns a signed Verdict, so the decision is evidence, not vibes.
What happens when the data can't support a decision?
The run comes back honest-empty: if nothing clears the lift bar, the engine refuses with structured reasons instead of returning weak rankings — and the run is refunded. A refuse band bills nothing. Refusing to guess is the feature, not a failure mode.
Do I need an account or an API key to try it?
No signup. Add the connector URL to Claude, ChatGPT, or Cursor — or run uvx hunter-seeker sample in a terminal. About sixty seconds later you have a signed Verdict on a free sample dataset. No email, no dashboard.
How do I verify a Verdict?
Any Verdict can be checked without credentials: call hs_verify_verdict over MCP, or verify offline with the open-source libraries hs-verify (pip) and @hunter-seeker/verify (npm) against the public keys at hunter-seeker.net/.well-known/jwks.json. Verification returns valid, invalid, expired, or unknown-key — nothing else, so the endpoint cannot be probed.