Skip to content
API is live

GRACE API

Embed the decision engine in your stack. Host data in your environment and call the GRACE engine, or run everything in GRACE's secure hosted environment.

Quick Start Request Access 
# Example request
curl -X POST "{{BASE_URL}}/engine/decision" \
  -H "Authorization: Bearer <API_KEY>" \
  -H "Content-Type: application/json" \
  -d '{
    "case_id": "A-12345",
    "segment": "floorplan",
    "policy": "v1",
    "inputs": { "balance": 150000, "past_due_days": 12 }
  }'

# Example response
{
  "case_id": "A-12345",
  "action": "short_cure",
  "rationale": "Approval criteria met vs. enforcement baseline",
  "policy": "v1",
  "audit_ref": "dec_9f3a..."
}

Hosting Models

Pick the setup that fits your data residency and operations. Both models return the same decision output.

API-Only (Customer Hosted Data) Data stays with you

Data location
Your databases, lakehouse, or message bus
What GRACE receives
Minimal case payloads to evaluate; no bulk storage by default
Persistence
You store the result; GRACE returns an audit_ref for review
Access
Outbound HTTPS to GRACE with an environment-scoped API key
Best for
Strict data residency, mature internal pipelines

Managed Environment (GRACE Hosted) Fully managed

Data location
GRACE VPC with encryption at rest and governed access
What you send
Scheduled ingests or feeds for the segments you run
Persistence
Full audit logs retained; policies versioned and queryable
Access
API keys and optional SSO with IP allowlisting
Best for
Faster rollout, centralized governance and reporting
  • Encrypted at rest and in transit
  • Auditable policy versions and decision logs
Same API, same outputs. Choose the environment that matches your controls today.
You can change models later. We support phased migrations.

Quick Start

1. Request Access

Provision an API key, choose hosting, and receive your sandbox base URL.

2. Map Fields

Align essential inputs for your segment. Keep it minimal at first.

3. Test and Promote

Validate decisions, review audit records, and promote to production.

Endpoints Overview

POST {{BASE_URL}}/engine/decision
Authorization: Bearer <API_KEY>
Content-Type: application/json

{
  "case_id": "A-12345",
  "segment": "floorplan",
  "policy": "v1",
  "inputs": { "balance": 150000, "past_due_days": 12 }
}

Note: Base URL and full schemas are provided during onboarding. Examples above illustrate shapes without exposing production details.

Authentication and Access

Capability Customer Hosted GRACE Hosted
Data residency Customer environment GRACE managed
Engine access API only API + managed runtime
Backups Customer managed Managed by GRACE
Audit logs API references returned Full logs retained
Policy versioning Queried via API Managed and queryable
SLAs Per contract Published onboarding SLAs

Ready to integrate?

Choose your hosting model and request access. We will provide base URLs, credentials, and implementation guidance.

Request Access See Use Cases