Trinsic Core is infrastructure for digital trust. It's our set of APIs for sending verifiable data between digital identity wallets. Core gives people and organizations the ability to easily and securely prove things about themselves with digital credentials.

With Core, you can transform credentials, licenses, passes, and certificates into a W3C standard format that can be exchanged digitally and verified instantly by anyone called a "verifiable credential".

Below is our two technology stacks for Trinsic Core.

Trinsic Core v1

Trinsic Core v1 is our original Trinsic Core tech stack and supports some of the largest digital credential implementations in the world. It consists of three APIs for digital credential exchange.

Credentials API

The Credentials API gives you the ability to spin up enterprise agents hosted on our servers but controlled by you. These enterprise agents are capable of managing complex workflows related to DIDs (contacts/ConnectionConnection - A connection is a peer-to-peer relationship using a pairwise key exchange. It is the most secure way to offer, issue, and verify credential. The process of establishing connections is described in Aries RFC 0023: DID Exchange Protocol 1.0.s) and VCs (credential issuance, RevocationRevocation - Revocation is the act of an issuer invalidating a credential they've issued. The holder of the credential isn't notified and the credential can still be used. However, when it's used, the holder will be unable to prove it hasn't been revoked. This is similar to when a driver's license is revoked due to driving under the influence; although the holder of the credential can't use it to drive a vehicle, they still might use it to prove that they are over 21, for example (as long as the verifier is OK that it's revoked!)., VerificationVerification - A verification is the general term used by Trinsic to describe the act of verifying or checking the legitimacy of a credential (or a proof). Our products abstract away a lot of this complexity, but the protocol we use under the hood is described in the Aries RFC 0037: Present Proof Protocol 1.0 and is summarized as follows: 1. Propose proof (optional) 2. Proof request 3. Proof presentation 4. Ack (optional), etc).

This is our flagship product because VC IssuanceIssuance - An issuance is the action of sending a credential from one party to another. Trinsic's products make the process simple. Under the hood, it uses Aries RFC 0036: Issue Credential Protocol 1.0, which can be summarized in the following steps: 1. Propose credential (optional) 2. Offer credential 3. Request credential 4. Issue credential 5. Ack (optional) and verification are at the core of every SSI use case. In addition, our competitors are charging an arm and a leg for these credentials, so our providing this service at a fraction of the cost is a huge competitive advantage for us from a growth perspective. Most of the users utilizing the Agency Feature will be building verification use cases. Currently, almost every user does both issuance and verification.

Check out the documentation of this API here.

Provider API

The Provider API is a Trinsic product that gives you your own AgencyAgency - An agency is a service that creates agents on your behalf. The Provider API gives developers their own agency that they can use to provide SSI capabilities to their stakeholders., enabling you to become an SSI provider to your stakeholders. It is authenticated to using a secret key accessible via the Trinsic Studio. Its primary functions are to create, delete, and manage OrganizationOrganization - An organization is a Trinsic-hosted agent controlled by a legal entity and provisioned with the capability to engage in credential issuance and verification. It is synonymous with tenant in the Trinsic platform.s.

Check out the documentation of this API here.

Wallet API

The Wallet API provides an organization the ability to act as a custodian of its users' WalletWallet - Software that securely stores credentials. It also stores identifiers, proofs, messages, and other information exchanged between two agents.s. This API lets you create cloud agents that can hold credentials, make connections, and respond to incoming messages like proof requests.

Check out the documentation of this API here.

Standards and protocols

The digital identity standards and protocols that make up Trinsic v1 include JSON credentials, CL signatures, Hyperledger Aries exchange protocols, and DIDComm v1.

🛠 Getting started

Sign up for a free Trinsic Studio account by clicking the "Studio" button in the top-right of your screen or this link and then visit our API reference documentation.

Trinsic Core v2 (in private beta)

Trinsic Core v2 is the largest upgrade to Trinsic Core since our launch in 2019 and is the next generation of digital trust infrastructure powered by the latest emerging standards. The benefits of Trinsic Core v2 include more scalability, interoperability, and better performance.

Standards and protocols

The digital identity standards and protocols that make up Trinsic Core v2 include JSON-LD credentials, BBS+ signatures, Presentation exchange, and DIDComm v2.

Join the waitlist

Trinsic Core v2 is currently in private beta. Join the waitlist at the bottom of our Trinsic Core page on our website to receive more information about its availability.

Did this page help you?