Read it before you believe it.

One page per wall. Every rule identifier, baseline feature, scoring weight, schema field and endpoint on these pages was read out of the source rather than written for a brochure. This is the surface where you check us against ourselves.

Scope an engagement See the perimeter

Ops Monitor

Three layers in a fixed order over the operational surface: signers, governance, the served frontend, and the RPC feeds your contracts read.

Operational sensing

Exposure Map

A dependency graph grown live from mainnet with provenance on every edge, a look-through exposure API over it, and a cascade simulator that runs the breach forward.

Contagion & exposure

Asset Ratings

Machine-readable minimum standards for the cross-chain infrastructure you build on, scored from a public methodology and watched for drift.

Configuration floors

AI Agent Guardrails

Every AI agent bound to an accountable operator, and wrapped in constraints enforced at validation rather than requested politely at the SDK.

Agent identity & guardrails

Live Detection

One detection core, four lanes, five layers in a fixed order. The only module that works upstream of finality, and the only one with a Solana rule set.

Pre-inclusion detection

Platform references.

The references that belong to no single wall: the HTTP surface, the typed clients, and the artefacts an auditor asks for. Same shape as the pages above, because they are the same kind of document.

API reference

One authenticated HTTP surface across the platform. Every route names the capability it needs rather than a role, so adding a role can never silently widen an existing route.

HTTP

SDK reference

Typed clients for the two synchronous lanes: gate an AI agent before it acts, and get a pre-signature verdict before a user signs.

TypeScript

Attestation format

The threshold-signed, expiring envelope every alert, rating and incident is delivered in. Verifying one needs our public key and nothing else.

Verification

Tenancy & residency

How a tenant is isolated, how a residency pin is enforced on every authenticated request, and exactly what an operator can and cannot see.

Platform

Compliance export

The hash-chained record of every screening, verdict and action Fuga Labs took, with whole-chain verification on export.

Audit

Onboarding presets

The eleven presets, their configuration schema, the detector set each puts in play, and the perimeter each declares.

All verticals

How to read these pages.

Three rules, and they are why the pages are worth the time it takes to check them.

The edge Every capability names its identifier.

Closed by If a page claims a rule, a feature or an endpoint, the exact identifier is on the page. A capability described only in prose is one you cannot verify, and this surface exists precisely so you do not have to take our word for anything.

The edge Every page states where its boundary sits.

Closed by The boundary is at the foot of each page in the same type as the capabilities, paired with the control that covers it. A reference that lists only what a thing does is a brochure with monospace in it.

The edge The identifiers match the product.

Closed by The rule identifiers here and the catalogue running in production are the same strings. Diff them; that is what they are for.

Public methodology stays public.

These references are open. Engine-level detail and the full catalogue are provisioned with your engagement, alongside the console your team works in.