Product
GateCore checks an agent's identity, permissions, policy, and authorized price before a routed request reaches your API. Your team can review the decision and verify the signed record.
An interface example. Not evidence of a production request.
A request can be allowed, held for configured review, or denied. A review approval releases that hold; remaining checks still apply when processing resumes.
Verify the request signature, freshness, replay state, registered key, and agent grant.
Resolve the agent, grant, and allowed capabilities from server-side records rather than trusting caller-supplied identity.
Evaluate the request against configured policy. The result can allow, hold for review, or deny.
Check the request's signed per-request maximum price and applicable funding path before configured-provider execution.
Call the API behind the capability through its configured provider connection. The provider enforces access at the resource.
Sign a record of the request, decision, and observed result. Your team can verify the record and compare the result with its recorded digest.
For a paid transaction, applicable settlement records the economic outcome. An authorization or a demonstration alone is not evidence that funds settled. Pricing and usage details.
Operators can inspect the purchase, agent, amount, and review deadline in the approval queue. Approving clears the review hold; the request continues through remaining checks.
Configure agent grants, capabilities, spending policy, and review thresholds for requests routed through GateCore.
Describe the capability, input contract, price, and access terms that a buyer can discover. Configure how requests reach the provider and enforce authorization at the protected resource.
Checks signed identity, grant scope, configured policy, and signed per-request maximum price before configured-provider execution; records the observed result.
Configure policy, review held actions, and inspect decisions and associated costs.
Lets compatible, configured clients discover published terms and submit requests through the connected workflow.
Discovery of published terms may be public. Accessing protected capabilities requires the configured client, identity, grant, and provider-side authorization for that route.
{
"mcpServers": {
"gatecore": {
"url": "https://mcp.gatecoreai.com/mcp"
}
}
}ENDPOINT https://mcp.gatecoreai.com/mcp
A signed receipt can be independently checked for its signature and bound request/result canonical-JSON hashes. That supports verification of the signed record's integrity; it does not prove an unobserved action did not happen or establish a target's real-world outcome.
Open the receipt verifier Review the recorded local demo evidence
Start with one provider workflow: identify the resource and routes to protect, configure the client and provider integration, register identity and grants, set policy and price limits, and confirm the evidence your team expects. Deployment and provider access depend on the selected configuration.
The film is an illustrative product presentation. For the bounded local recorded-demo evidence and its limitations, review the demo evidence.