ForgeAIrequest accessrequest access

platform · semantic markers

Build with Semantic Markers. Run them with your own agents.

ForgeAI gives builders and analysts the tools to define concepts, forge calibrated markers and run them as a control layer inside the agents and pipelines you already have. From the first request, on your own documents.

platform · semantic markers

01 / 07

Build with Semantic Markers. Run them with your own agents.

Define concepts, forge calibrated markers and run them as a control layer inside the agents and pipelines you already have.

inside the pipeline · tap a stage

Table Like: six detection maps with their cues, variants and examples
The concept graph behind every score299 nodes · 298 links

01 define · three layers

From unstructured text to structured signals.

Documents, emails, filings, transcripts. Three layers of semantic schema surface what matters in them. Each layer is a set of Semantic Markers; each marker is one concept with one calibrated score, traced to the passage that triggered it.

The model core only ever sees the text that matters: scored and filtered before inference, validated and explained after it.

From concept to production signalsdeterministic
01 · Define · concepts · three layers

Client experts define the concepts that matter. ForgeAI structures them into detection maps across three layers of schema: Base, Business and Custom.

01 define · three layers

02 / 07

From unstructured text to structured signals.

Three layers of semantic schema. Each marker is one concept with one calibrated score, traced to the passage that triggered it.

03 customproprietary knowledge
02 businessindustry semantics
01 basegeneral & regulatory

Industry semantics for your sector: supply-chain, counterparty and market risk, named the way your analysts name them.

calibrated signal · business
markersupply_chain_disruptionscore0.86 · valence negativetrace→ passage 14 · q3_filing.pdf

scored before inference · explained after it

02 forge · how a marker is forged

Every marker is forged from examples, not written as a prompt.

01Positive examples. Complete coverage of the concept.
02Hard negatives. Precision at the concept boundary.
03Edge-case variants. The underrepresented ways production phrases it.
04Synthetic example sets. Privacy-safe examples where real ones are scarce or restricted, so regulated teams forge markers without exposing data.
“No other commercial NLP product uses quality-diversity search. ForgeAI is the first.”not one best solution · a structured library of optimal policies
From examples to a production markermap-elites
positive examplescomplete coverage
hard negativesboundary precision
edge-case variantsproduction phrasing
map-elites archive
boundary precision →
narrow phrasingbroad phrasing →
elite per region26 of 28 regions filled
Production marker
supply_chain_disruption
separability · s0.91
coverage · c0.88
relevance · r0.84
production-ready
quality-diversity searchbest candidate kept per regionnot one best guess

02 forge · how a marker is forged

03 / 07

Every marker is forged from examples, not written as a prompt.

map-elites archive · quality × diversity28 / 28 cells
boundary precision →
narrow phrasingbroad phrasing →
production markersupply_chain_disruption
s0.91c0.88r0.84

Not one best prompt: a library of operating points. Precision, recall or balance — your call, per deployment.

“No other commercial NLP product uses quality-diversity search. ForgeAI is the first.”

03 govern · routing policy

You set the gate. The platform enforces it, every run.

Confidence thresholds, risk tolerance and review rules are configuration, not prompts. Every result is routed deterministically to automation, to a reviewer or to escalation, and the reason travels with it. Change the policy and the same passage takes a different, equally traceable path.

Try the dial: the three sample passages re-route as you change the policy.

Policy-driven routing with configurable guardrailsdeterministic
routing policy
prioritise automation
require confidence threshold
confidence threshold0.80
risk tolerancemedium
review required for
sample passages · 3effective threshold 0.80
Supplier X — Q3 reviewa9f3c1d2 · negative_projection · flag: reputation0.91automation
KYC file — counterparty 114c02d77e5 · regulatory_obligation · flag: legal0.86human review
Amended supply terms — March7be04a91 · regulatory_enforcement · no flag0.78escalation
path 1Automation1downstream
path 2Human review1queued
path 3Escalation1a person decides

03 govern · routing policy

04 / 07

You set the gate. The platform enforces it, every run.

the dial · configuration, not promptseffective 0.80
confidence threshold
risk tolerance
review required for
financial impact
legal / compliance
reputation risk
three passages · where they go now

Supplier X — Q3 reviewnegative_projection · flag: reputation

0.91automation

KYC file — counterparty 114regulatory_obligation · flag: legal

0.86human review

Amended supply terms — Marchregulatory_enforcement · no flag

0.78escalation

1 of 3 automation1 of 3 review1 of 3 escalation

04 build & integrate · your agents

Use it instantly with your own agents.

Nothing to migrate, nothing to rebuild. Your agents call the control layer over the API: context is gated on the way in, outputs are scored and vetoed on the way out. Your providers, your sources and your deployment pipeline stay exactly where they are.

integration · spec sheet · what your engineers will ask
api

REST API

Every call scored, vetoed and logged. Connect any backend system in a request; the audit feed comes with it.

sdk

SDK for front-end and back-end

Embed governed outputs in websites, dashboards, back-office systems and mobile apps.

your providers

Client-selected models

GPT, Claude, Gemini, Llama or Mistral, for LLM and embeddings alike. ForgeAI governs the workflow regardless of provider.

your agents

Orchestration frameworks

Your agents call the layer from the first request. Context is gated on the way in, so each agent sees only what it needs.

your sources

Files, databases, APIs, clouds

Document collections from your own stores. Ingestion pipelines, vector stores and data lakes on AWS, GCP or Azure.

ship

Version, test, deploy

Every app is versioned and tested before it ships, then deployed over the API with full logs and spend control.

04 build & integrate · your agents

05 / 07

Use it instantly with your own agents.

Nothing to migrate, nothing to rebuild. Your agents call the control layer over the API; your providers, sources and pipeline stay where they are.

spec sheet · what your engineers will ask01 / 06
rest · post /v1/score

REST API

Every call scored, vetoed and logged. The audit feed comes with it.

POST /v1/score
{ "text": "…", "schema": "business",
  "threshold": 0.85 }

→ { "score": 0.86, "verdict": "pass",
    "trace": "passage 14 · q3_filing.pdf" }

One call. Score, verdict and trace come back together.

05 the workspace

Define, forge, run and inspect in one workspace.

The editor where apps and markers are built, the run surface your analysts use, the concept graph behind every score, and the settings that connect it all to your stack.

forge · markers · concept graphEvery concept mapped, every link explorable299 nodes · 298 links
Table Like: six detection maps with their cues, variants and examples

05 the workspace

06 / 07

Define, forge, run and inspect in one workspace.

The ForgeAI editor: a node graph of inputs, prompts, functions and outputs for the app cv
Editorapps · markers · checkpoints

A node graph of inputs, prompts, functions and outputs. Checkpoints, preview, publish.

06 get started · your agents · day one

07 / 07

Connect your agents today.

Nothing to migrate, nothing to rebuild. Your agents call the control layer over the API from the first request, on your own documents.

rest api · sdkyour modelsyour sources