a trust score built from proof.

verified identity, sealed authority, and a record of what the agent actually did. a score that shows its work.

the problem

an agent shows up at your door with a name and a key. is it good for what it asks? today that answer comes from reputation lists and self-declared manifests, things the agent says about itself. that is not trust. that is marketing.

syenbuilds the score from what can be proven. identity is verified, authority is sealed with ed25519 before the agent moves, and every action chains with sha-256 into a record anchored daily to digicert’s rfc 3161 trusted timestamp authority.

what goes into the score
  1. 01identity

    a verified agent and operator, not a self-declared name.

  2. 02authority

    sealed mandates showing what the agent was cleared to do, before it did it.

  3. 03history

    a chained record of what it actually did, and whether it stayed in scope.

how it reads
an agent in scope

its record verifies end to end. that is the strongest signal there is.

an agent that drifted

the failed verifications are in the record too. the score carries them.

a new agent

no history, no score inflation. it earns the record one action at a time.

a checked agent

anyone can verify the inputs with openssl. the score shows its work.

independent verification

proof that stands on its own.

every input to the score verifies with openssl. no access to your systems. no access to ours.

ed25519 signatures·sha-256 chain·rfc 3161 anchoring·openssl verification
where teams use it

teams scoring agents at the door start by knowing the agent, issue the agent passport, and read the score off the audit trail. see the governed workflows on the use cases page.