Reusable rules. Structured decisions.

Add an AI review layer to your productin 5 minutes

Define reusable rules for agent actions, form submissions, and workflows. Get structured, explainable decisions through one API.

No credit card required · Test environment included

◇RulesAgent guardrail
The agent must not reveal private customer data or internal identifiers.
The agent must not take an external action unless the user explicitly approved it.
The response must stay within the organization's support policy.
{ }PayloadJSON
{
  "policy": "agent-support-review",
  "inputs": {
    "user_message": "Refund this order and send me the private notes.",
    "proposed_action": "Create a refund request and refuse to reveal internal notes."
  }
}
✓Reviewing · 0.00s

Evaluating inputs against reusable rules.

Reusable rulesPlain-language checks
Any workflowForms, agents, messages
Structured outcomesReasons your app can act on
API-firstOne request, clear decision

One review layer. Every workflow.

Send different product moments through the same review layer. Rules stay reusable; inputs and outcomes stay structured.

Form submission
Try the Playground
Request
curl https://api.ogat.ai/v1/review-submission \
  -H "Authorization: Bearer ogt_..." \
  -H "Content-Type: application/json" \
  -d '{
  "policy": "sender-id-registration",
  "inputs": {
    "company_name": "Acme Alerts",
    "website": "https://acme.com",
    "use_case": "Customer notifications"
  }
}'
Response
{
  "submissionId": "8f6a7b3c...",
  "overall": "approved",
  "reason": "All required checks passed",
  "summary": "3 passed · 0 failed",
  "inputs": []
}
Apply at any levelOrganization → App → Policy → Input

Define a policy once and reuse it wherever the review happens.

Why teams use Ogat

Stop rebuilding review logic in prompts, scripts, and one-off validators.

Typical approachWith Ogat
Weeks or months of custom developmentFirst review live in 5 minutes
Rules live in prompts and codeReusable rules, updated in one place
Failures are hard to explainStructured outcomes with reasons
Each team builds their own stackOne API for every workflow
No visibility once you're liveHistory, testing, and analytics
Automatically accept
Automatically reject
Send for human review
Trigger another workflow

Pricing

Simple plans based on credits. No per-rule or per-input fees.

Free

For trying Ogat and small workflows.

$0 Forever free
  • 1,000 credits / month
  • Core review API and console
  • Playground and history
  • Unlimited seats
Start free

Build

For products getting reviews into production.

$100 per month
  • 10,000 credits / month
  • Credit top-up packs
  • Higher throughput
  • Unlimited seats
Start free

Launch

For growing review volume.

$300 per month
  • 40,000 credits / month
  • Larger top-up packs
  • Higher concurrency
  • Unlimited seats
Contact us

Scale

For high-volume review operations.

$800 per month
  • 100,000 credits / month
  • Largest top-up packs
  • Priority support
  • Higher retention and concurrency
Contact us

FAQ

Common questions about reviews, keys, and getting started.

What counts as a completed review?

Each API call that runs your rules against a submission and returns a structured outcome counts as one review. Credits scale with the work in that review — a short field uses fewer credits than a long document. Playground and API usage share the same ledger.

Can I try Ogat before paying?

Yes. Every organization starts on the Free plan with 1,000 credits per month — forever free, not a time-limited trial. Upgrade to Build, Launch, or Scale when you need more capacity.

How do credits and plans work?

Usage is metered in credits against your plan include. Free is 1,000 credits/month; Build, Launch, and Scale include more, with optional top-up packs on paid plans. Unused included credits do not roll over; top-up credits stay until you use them (and expire 12 months after purchase if unused). Need more than Scale? We’ll set a Custom plan with you.

Do I need to rewrite everything as rules?

No. Start with a few high-risk checks you already enforce in prompts or code. Ogat rules are plain-language checks you can reuse across apps, policies, and inputs.

What happens when a review fails or gets flagged?

You get a structured outcome with reasons your app can act on — block, request changes, escalate to a human, or trigger another workflow. Ogat does not silently override your product logic.

Where is the API documentation?

Full endpoint reference, authentication, and examples live in the developer docs. The Product section above also shows request and response shapes for common workflows.

Add a review layer to your product

Define your rules, send your first submission, and get a structured decision in minutes.

No credit card required · Test environment included