Questions, answered plainly.

GateCore checks an agent's identity, permissions, policy, and authorized price before a routed request reaches its provider. Your team can review the decision and verify the resulting signed record.

GateCore brings signed agent authority, permission checks, policy, a per-request price ceiling, and verifiable receipts into one request flow. It can work alongside your gateway and workflow tools. The integration defines which requests pass through GateCore and how the provider enforces access.

GateCore gives authorized agents a controlled route to your data. Your existing protection still needs to cover public pages, direct credentials, and other routes outside GateCore. We help define how that governed route fits your access controls.

Compatible MCP clients can connect to GateCore's endpoint and supported tools. Public listing terms are available for discovery; purchases and protected capabilities require the appropriate account, permissions, and funding. The connection guide covers supported setup paths.

Yes. A policy can hold a request for operator review. Approval clears that hold, and the request continues through its remaining checks. See the console workflow.

Yes. The marketplace is optional. Start with an internal agent and a capability it needs to access, then configure the route, permissions, and policy for that workflow.

The provider keeps its data and defines what the capability accepts, returns, and permits. GateCore's listing and request checks reflect those terms. Authorization at the underlying resource remains part of the integration.

Choose a capability and connect its provider route. Then register the agent, grant the access it needs, and define policy and price limits. Your client and resource controls determine the integration work. Start with the docs, quickstart, or MCP guide.

It lets you check the integrity of the signed record and the request and result it binds. The receipt records what GateCore observed; verifying it does not establish the truth of the underlying data or a separate real-world outcome. Try the verifier.

No. It shows actual GateCore code running locally with a fictional provider and test data. No customer payment occurs. The evidence page explains the checks, results, and scope.