Legal
API terms
Version 2026-10-30 · Last updated October 30, 2026
These terms apply when you use the Neptuv API, MCP server, SDKs, widgets, badges or data exports, and are part of the Terms. Technical details are in the docs.
Keys
- API keys belong to your account. Keep them secret: never put them in client-side code, public repositories or apps you ship to users. You're responsible for all use of your keys.
- Revoke a key from your dashboard as soon as you think it has leaked. We may revoke keys we find exposed or misused.
Limits
Each plan includes the call limits shown on the pricing page; the free tier is limited per IP address. Other limits (for example on exports, sign-ins and test alerts) protect the service. Calls over a limit are refused, not charged. Don't use multiple accounts or keys to get around limits.
What you may do with the data
- Use scores, labels, reasons and verification results inside your own product to decide which agents to trust, show them to your own users, and cache them for up to 24 hours.
- Show the official badge or widget on the page of the agent it belongs to.
- When you show a Neptuv Score publicly, credit it as "Neptuv Score" with a link to the agent's page on neptuv.xyz, and don't change the score or label.
What you may not do
- Resell, sublicense or redistribute Neptuv data in bulk, or use it to build or train a competing scoring, rating or reputation dataset.
- Present Neptuv data as your own, or as more current, complete or certain than it is.
- Use the data about natural persons (such as agent owners) for credit, employment, insurance, housing or similar eligibility decisions, or to profile them.
- Anything the Acceptable Use Policy forbids.
Your responsibility for decisions
Allow/deny answers, verifications and attestations apply rules you choose to data that can be wrong. You decide what happens in your product and you are responsible for the outcome. See the Disclaimer.
Changes and availability
We aim to keep the API stable and will announce breaking changes on the changelog at least 30 days ahead where we reasonably can. The API is provided "as is", without a service-level guarantee; see the Refund Policy for plan-time credits after long outages.
Ending access
You can stop using the API at any time. We may suspend or end API access for breach of these terms, as set out in the Terms. When access ends you must stop using cached Neptuv data within 24 hours.