Skip to content
Controlled coverage evidence · verified 16 Sep 2026
114/194 accepted · 80 fail-closed

114 sovereign countries passed the current four-module Risk Gate review census.

A controlled workflow evaluated all 194 enabled sovereign countries; 80 remained fail-closed. Missing or unverified inputs are not converted into approval, and every accepted result keeps execution_authorized=false.

Review Risk GateEvidence & limits

This evidence did not activate x402, real-money payments, Base mainnet or autonomous execution. Claim boundary: this is a dated controlled-workflow coverage result for the current Risk Gate methodology. It is not an all-country product guarantee, transaction authorization, production SLA, independent security audit or mainnet-launch claim, and it does not imply that every product is deliverable for every accepted country or request shape.

PRIVATE PILOT

Check external risk before a financial action moves forward.

Risk Gate is Geomacro's controlled decision-context layer. The Private Pilot verifies a signed country or corridor Risk Object and returns bounded risk context. The customer's own identity, permissions and policy layer decides what happens next, and the customer keeps control of execution.

Not generally available production software. The current corridor model compares endpoint risk and eligible bilateral evidence. It is not full route, logistics, counterparty, sanctions or compliance analysis. Event-specific Risk Objects are not in the current controlled scope.

LIVE NOW

Risk Intelligence

Public event intelligence, evidence and current risk context can be evaluated today.

Learn more

LIVE NOW

Separate Risk Indices

Geopolitical, macroeconomic and critical-mineral risk are published separately.

Learn more

PRIVATE PILOT

Risk Gate

Controlled validation exists, while general production availability remains gated.

Learn more

Private Pilot workflow

Risk context in. Customer decision out.

STEP 1

Action to review

A treasury system, payment workflow or agent submits a country or directional-corridor context for review.

STEP 2

Geomacro verifies context

Risk Gate checks the Risk Object, signature, methodology, freshness and required inputs, then returns bounded decision context.

STEP 3

Customer stays in control

The customer's own identity, permissions and policy layer applies its rules and controls any downstream action.

Control boundary

A risk recommendation is not permission to move money.

Geomacro supplies external geopolitical and macro risk context. It does not own customer identity or permissions, hold funds, sign a customer wallet, replace sanctions/compliance screening, or make the customer's final fiduciary decision.

execution_authorized = false
CONTINUE
REDUCE_LIMIT
REQUIRE_APPROVAL
PAUSE

PRIVATE PILOT

Signed Risk Objects

Versioned and Ed25519-signed objects let a receiving system verify the issuer and inspect the context it received.

CONTROLLED SCOPE

Country + directional corridor

The controlled scope covers country subjects and directional corridors composed from endpoints plus eligible bilateral evidence. Full physical-route and counterparty modelling are not claimed.

PRIVATE PILOT

Fail-closed controls

Authentication, validation, rate limits, signature and freshness checks, and audit records are part of the controlled design. Unverified context must not silently become approval.

VALIDATED IN CONTROLLED PRIVATE PILOT

What exists today

  • • signed Risk Object creation and verification
  • • authenticated country and directional-corridor interfaces
  • • database-backed per-client rate limiting
  • • immutable decision-audit contract design
  • • fail-closed pre-flight risk evaluation
  • • customer-owned identity, permissions, policy and downstream execution

PRODUCTION LAUNCH GATES

What must be completed before launch

  • • independent security review of externally reachable surfaces
  • • real staging HTTP/database load and resilience evidence
  • • final commercial source-rights clearance for paid delivery
  • • broader corridor-methodology validation
  • • design-partner and willingness-to-pay validation
  • • production operations and SLA evidence before any SLA claim

DESIGN PARTNERS

Have one real country, corridor or treasury decision to test?

A Private Pilot is for validating a narrow workflow and its business value. It is not a production deployment or a promise of general availability.

Discuss the workflow