# Overview

## Platform

Tephra securely manages the creation and transfer of digital assets. Every transaction is stored in the [Tephra](https://tephra.co) Changeset. **We regularly preserve the changeset with the same tools auction houses use to secure multi-million dollar artworks (ETH/IPFS).** We've taken careful steps to ensure these preserves will exist into the distant future.

```typescript
// Import our SDK
import { TephraSDK } from '@tephranet/tephra-sdk'

// Authenticate
const tephra = new TephraSDK(KEY, SECRET)

// Create an asset
const myPainting = await tephra.create({
  name: 'Spirt World - Digital Painting',
  image: {
    type: 'ipfs',
    address: 'Qme7ss3ARVgxv6rXqVPiikMJ8u2NLgmgszg13pYrDKEoiu',
  },
})

// Grant the asset
await tephra.grant(myPainting, "Daphne")

// Transfer the asset
await tephra.transfer(myPainting, "Daphne", "Velma")
```

## Key Features

### 👻 No Accounts Required

Keep your account provider. We don't store any user data. You only need to provide Tephra with user IDs that are meaningful to your platform when granting and transferring assets. *(see* [***Grants & Transfers***](/tephra-sdk/getting-started/grants-and-transfers.md)*)*

### 🔐 Rich History & Validation

Each asset has its own unique validation page. This page is styled to match your branding, and displays the contents of the asset (an image, text, structured attributes, etc) along with the full record of ownership. *(see* [***Validation***](/tephra-sdk/getting-started/validation.md)*)*

### 📈 Massively Scalable

We can provide accounts to meet virtually any scale requirements. You could manage anywhere from a few assets to a few hundred thousand without changing your integration.

### 🧰 Built for Integration

We've crafted our APIs to extend your digital experience, not to replace it. Combined with modern e-commerce platforms and payment providers, It will produce innovations worthy of your brand.

### 🏝 Portable to Other Markets

If you choose, customers can "eject" assets from Tephra to be bought and sold elsewhere. When an asset leaves our network, we store the date/owner at the time of ejection and maintain the Tephra address as a Certificate of Authenticity. *(see* [***Ejecting***](/tephra-sdk/getting-started/ejecting.md)*)*


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://tephra.gitbook.io/tephra-sdk/master.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.