Readable for people.
Structured for agents.
The links below explain what each machine-readable endpoint does. You can stay on this page; agents and developers can open the raw data when they need it.
How an agent learns Vigil.
Agent instructions are a short text guide for software. They describe available tools, how to connect, prices, limits, payment behavior, and safe retry rules. The raw file can look plain because it is written to be copied into an agent’s context.
Open machine-readable agent instructionsThe exact shape of every request.
The Agent API contract is an OpenAPI document. It tells software which fields are allowed, which responses can return, and what errors mean. The dense JSON is useful to code generators and agent runtimes; most people will prefer the examples in the developer guide.
See the human-readable integration guide
Open raw OpenAPI JSONWhat agents can buy right now.
Live capabilities reports the currently deployed price, networks, limits, methodology, and input/output schemas. Agents should check it immediately before paying because it reflects the running service.
Available on Base and Solana mainnet through x402. Live owner-funded purchases have settled and returned independently checked signed receipts. Independent buyer demand, a third-party security audit, and long-term availability have not yet been established.
Vigil is published as com.vigilnotary/vigil in the preview official MCP Registry. Its paid HTTP resource is also configured for x402 Bazaar discovery; Bazaar catalog ingestion and ranking are controlled by Coinbase and may lag a successful settlement.
Run the public integration examples before putting the service in an automated workflow.
Open raw live capabilities JSONOne MCP address.
Agent tools connect to https://vigilnotary.com/mcp using Streamable HTTP. Opening that URL like a web page may show protocol data or an error because it is a software connection, not a human page.