Public permit lookupAgent → GateCore → Your records service
What this makes possible
Control agent access. Keep the boundaries clear.
Start with a public record that can be shared through an approved connection. Agree on the permission and review requirements before setup.
01
Know who is asking
Verify the signed agent request against its configured identity and access grant.
02
Set the permitted action
Check the granted scope and per-request price ceiling before the connected API runs.
03
Keep an inspectable record
Link the request and observed result through a signed receipt you can verify.
Worked example · fictional data
A useful first workflow.
A proposed public permit lookup integration. No customer result or live transaction is represented.
01
Who
A records clerk in fictional Westhaven asks an assistant for one public permit summary.
02
The request
Find public permit PM-204.
03
The checks
GateCore checks the signed identity, granted scope and per-request price ceiling before calling the connected provider.
04
The record
The signed record connects the request to the response the gateway saw. Your team still decides how to retain records and meet its legal obligations.
Fits into your existing systems
Your systems. Your business rules.
GateCore holds no FedRAMP, FISMA authorization or agency ATO. Your agency controls records disclosure and whether a capability may carry a price. Confirm procurement requirements before planning an integration.
Sends a request under a configured identity and grant.
02
GateCore
Checks permitted access and the authorized request price.
03
Your records service
Handles the permitted call and supplies its response.
A few useful answers
Before you begin.
How does this fit our existing API?+
GateCore adds identity, grant, scope and price checks to requests routed through it. Your API continues to supply the result and enforce its own data-specific rules.
What would we start with?+
Start with a public record that can be shared through an approved connection. Agree on the permission and review requirements before setup.
How is GateCore priced?+
Gateway plans cover governed request usage. Providers can list a capability without a listing fee; optional seller services and marketplace settlement fees are separate. See plans and pricing↗
Start a conversation
Start with one useful capability.
Bring the workflow and the systems involved. We will work through the integration and the controls it needs.
