Trinsic

The Trinsic Docs

Welcome to the Trinsic Docs. You'll find comprehensive guides and documentation to help you start working with Trinsic as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    API Reference

Introduction

Welcome to Trinsic

We make it easy to implement Self-Sovereign IdentitySelf-Sovereign Identity - Self-sovereign identity (SSI) is a movement that claims digital identity should be just as legitimate and nuanced as a person’s human identity, while being accessible to all, privacy-preserving, and not reliant on a single government or corporation. based on Decentralized IdentifiersDecentralized Identifiers - A kind of identifier that is controlled by its subject (or assigns) and doesn't depend on a centralized registry, identity provider, or certificate authority. Each organization created in the Trinsic platform has a public DID written to the network it's setup on. Connections leverage pairwise, private DIDs to facilitate message exchange. Learn more at the Decentralized Identifiers W3C Spec Abstract. (DIDs) and Verifiable CredentialsVerifiable Credentials - A credential is a set of attributes about someone or something. Typically, credentials are digital versions of physical licenses, cards, documents, or certificates, but they can represent all kinds of abstract data. They are based on the W3C VC Data Model. (VCs), a new digital identity standard. Our software is based on the open-source Hyperledger Aries project, to which we are a primary contributor.

Together with proper governance, SSI enables, for the first time, the Trust over IPTrust over IP - Trust over Internet Protocol, or ToIP, is a play on the "Voice over IP" or "VoIP" terminology; it is an architecture internet-scale digital trust defined by the Trust over IP Foundation and Aries Concept 0289: The Trust Over IP Stack. Self-sovereign identity is a subset of Trust over IP focused on the human identification use case. (ToIP) stack. Once trust can effectively be conveyed over IP, a tremendous number of opportunities arise in every industry vertical imaginable. We build the tools to help you capitalize on this opportunity.

We make it easy for you to issue Verifiable CredentialsVerifiable Credentials - A credential is a set of attributes about someone or something. Typically, credentials are digital versions of physical licenses, cards, documents, or certificates, but they can represent all kinds of abstract data. They are based on the W3C VC Data Model. on behalf of your organization. These credentials can be used by individuals to prove things about themselves anywhere. We're built on an open source standard, which makes these credentials useful anywhere this standard is supported.

👍

Getting started

We're developers passionate about building a good developer experience, which means you can get started fast for free. Click the "Studio" button in the top-right of your screen or this link to get started.

Our Products

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.

📘

Get started in 15 minutes

Want to get started using digital credentials quickly? Try our Tutorial to get a conceptual walkthrough of a common use case.

Updated a day ago


Introduction


Welcome to Trinsic

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.