Architecture overview
Five layers, one harness
Integration patterns
Three ways to build
Connect a tool (MCP Server)
Expose your procurement tool — ERP, CLM, risk platform, analytics engine — as an MCP server. SIGNET agents discover and use your tool through the standard Model Context Protocol interface. Authentication, rate limiting, and permission boundaries are handled by the harness.
{
"name": "acme-clm",
"version": "1.0",
"description": "Contract lifecycle management",
"capabilities": [
"contract.search",
"contract.extract",
"obligation.list"
],
"auth": { "type": "oauth2", "scopes": ["read:contracts"] }
}Deploy an agent (Agent Card)
Register your AI agent in the SIGNET agent registry. Agents declare their capabilities via A2A Agent Cards, are governed by the rules engine, and produce immutable audit trails. All agents operate within sandbox boundaries determined by their category and entity scope.
{
"name": "procurement-negotiation-agent",
"description": "Negotiates within governed parameters",
"capabilities": ["negotiate.price", "negotiate.terms"],
"constraints": {
"max_discount": "15%",
"requires_approval_above": "£500K"
},
"audit": true
}Build an integration (Workato Recipe)
Use Workato's 1,200+ pre-built connectors or build custom recipes to bridge your systems with SIGNET. Event-driven architecture: subscribe to procurement events (supplier.registered, bid.submitted, contract.awarded) and trigger downstream actions in your systems.
// Subscribe to SIGNET events
on("contract.awarded", async (event) => {
await erp.createPurchaseOrder({
supplier: event.supplierId,
value: event.awardValue,
terms: event.contractTerms,
});
});Standards references