Review
Submit regulated content and receive findings, cited basis, suggested changes, status, and a canonical record.
Enterprise Agent Gateway
Connect your content agents to accountable review.
Upstream agents and content systems can submit Review, Create, and Update jobs through private REST or MCP. Redcliffe returns a structured result and keeps final approval with the customer’s accountable reviewer.
Private Enterprise accessREST or MCPReviewable records
Agent Gateway job
UK FinProm · Review
Submitted by
Campaign content agent
Scoped client · REST
Content
Our portfolio is expected to deliver 8% annual returns.
Structured result
- Status
- completed
- Findings
- 3 · 1 high risk
- Record
- structurally complete
- Approval
- redcliffeApproved: false
pending_customer_triage
The assigned customer reviewer decides findings before approval.
Contract
Versioned and machine-readable
Credentials
Account, project, model, and scope
Decision
Customer reviewer remains accountable
Where it sits
A compliance checkpoint between creation and publication.
Agent Gateway is not a second model or a public developer API. It is a private route into the same specialist models, records, and customer review boundary used in the Redcliffe workspace.
Content agent
Campaign workflow
CMS or DAM process
REST or MCP
Agent Gateway
Scope · model · mode · entitlement · audit
Structured result
Record and handoff
Findings, cited basis, suggested action, reviewer status, and exports.
One private contract
Three governed jobs, one model boundary.
Enterprise clients can enable the modes their workflow needs. The Agent-to-Record Pilot stays deliberately Review-first so the first proof tests the highest-value control without widening scope.
Create
Generate a controlled draft from a structured brief using the project’s enabled model and currentness path.
Update
Reuse proven content for a new season, year, offer, or audience, with changes and cited sources returned.
Machine-readable, human-accountable
The useful unit is the record, not the API call.
A caller can poll status, receive a signed callback, or fetch the result directly. Customer content and raw findings stay behind the authenticated Gateway rather than being pushed inside webhook payloads.
Authenticated readback
redcliffe.review_record.v1
- Job status and stable machine identifiers
- Structured findings, severity, and cited basis
- Suggested changes or generated draft output
- Canonical record and supported exports
- Human-review request and resulting customer status
- Signed status callbacks where configured
The boundary is the product
Useful to agents. Accountable to people.
External access is explicitly enabled, rate-limited, audited, and fail-closed. The machine client can move work and evidence; only the customer’s authorised people can make the final decision.
Account-scoped credentials
Keys are created for one customer account, shown once, stored as a hash, and limited to approved scopes.
Project and model boundaries
Every job is checked against the key, account, allowed project, enabled model, mode entitlement, and rollout gate.
Customer-owned approval
Agents can request human review and read the resulting status. They cannot approve, sign off, suppress findings, or publish.
A focused first engagement
Prove one agent-to-review workflow before Enterprise.
The Agent-to-Record Pilot tests whether one real upstream workflow can produce reliable records and usable customer handoffs. It is paid proof, not an open API trial.
GBP 5,000ex VAT · paid upfront
Commercial summary only. Activation is subject to the signed pilot order form, data-processing terms, security scope, and agreed prerequisites.
Agent-to-Record Pilot
One bounded production proof
- 30 calendar days from activation
- One live UK model and one Redcliffe project
- One upstream Review-first workflow
- One primary REST or MCP transport
- Up to 100 accepted Review jobs
- Named customer reviewer and human handoff
- Optional signed status webhook endpoint
- No automatic renewal or automatic overage
100% conversion credit
The pilot fee is credited against the first year of an Enterprise Agent Gateway agreement signed within 30 days of pilot end. Enterprise starts from GBP 30,000 per year; final scope and pricing depend on workflows, volume, models, and support.
Bring one real workflow
See whether your agent can produce a record people can rely on.
We will qualify one upstream content workflow, one live UK model, the accountable reviewer, and the integration route before proposing the pilot.