# Get identity graph by Farcaster id
Source: https://docs.memoryproto.co/api-reference/memory-api/endpoints/identity-graph/get-user-identity-graph-by-farcaster-id
get /identities/farcaster/fid/{fid}
Retrieve the identity graph for a user based on their Farcaster user ID.
# Get identity graph by Farcaster username
Source: https://docs.memoryproto.co/api-reference/memory-api/endpoints/identity-graph/get-user-identity-graph-by-farcaster-username
get /identities/farcaster/username/{username}
Retrieve the identity graph for a user based on their Farcaster username.
# Get identity graph by Lens username
Source: https://docs.memoryproto.co/api-reference/memory-api/endpoints/identity-graph/get-user-identity-graph-by-lens-username
get /identities/lens/{username}
Retrieve the identity graph for a user based on their Lens username.
# Get identity graph by Twitter username
Source: https://docs.memoryproto.co/api-reference/memory-api/endpoints/identity-graph/get-user-identity-graph-by-twitter-username
get /identities/twitter/{username}
Retrieve the identity graph for a user based on their Twitter username.
# Get identity graph by wallet
Source: https://docs.memoryproto.co/api-reference/memory-api/endpoints/identity-graph/get-user-identity-graph-by-wallet
get /identities/wallet/{address}
Retrieve the identity graph for a user by providing a wallet identifier. This can be an Ethereum address, an ENS domain, or a Basename.
# Get identity graph by Zora username
Source: https://docs.memoryproto.co/api-reference/memory-api/endpoints/identity-graph/get-user-identity-graph-by-zora-username
get /identities/zora/{username}
Retrieve the identity graph for a user based on their Zora username.
# Get credits
Source: https://docs.memoryproto.co/api-reference/memory-api/endpoints/social-graph/get-credits
get /credits
Retrieve the number of credits available to your organization.
# Get Farcaster Followers
Source: https://docs.memoryproto.co/api-reference/memory-api/endpoints/social-graph/get-farcaster-followers
get /farcaster/followers
Retrieve the Farcaster followers of an account by username or fid. If the followers aren’t already stored in our system, the request will queue a background job and return a `queued` status. As soon as fetching begins, the status becomes `in_progress`, and partial results are available, use the `progress` field to track completion. Once all followers have been retrieved, the status changes to `completed`. The maximum age of stored followers is 30 days.
# Get Farcaster Followers Status
Source: https://docs.memoryproto.co/api-reference/memory-api/endpoints/social-graph/get-farcaster-followers-status
get /farcaster/followers/status
Check the indexing status of Farcaster followers for an account. This endpoint does not trigger a new queue and does not cost credits. Returns 404 if the user has never been queued.
# Get Farcaster Following
Source: https://docs.memoryproto.co/api-reference/memory-api/endpoints/social-graph/get-farcaster-following
get /farcaster/following
Retrieve the Farcaster following of an account by username or fid. If the following aren't already stored in our system, the request will queue a background job and return a `queued` status. As soon as fetching begins, the status becomes `in_progress`, and partial results are available, use the `progress` field to track completion. Once all following have been retrieved, the status changes to `completed`. The maximum age of stored following is 30 days.
# Get Farcaster Following Status
Source: https://docs.memoryproto.co/api-reference/memory-api/endpoints/social-graph/get-farcaster-following-status
get /farcaster/following/status
Check the indexing status of Farcaster following for an account. This endpoint does not trigger a new queue and does not cost credits. Returns 404 if the user has never been queued.
# Get Farcaster Profile
Source: https://docs.memoryproto.co/api-reference/memory-api/endpoints/social-graph/get-farcaster-profile
get /farcaster
Retrieve the Farcaster profile of an account by username or fid.
# Get tweet details
Source: https://docs.memoryproto.co/api-reference/memory-api/endpoints/social-graph/get-tweet-details
get /twitter/tweet
Retrieve the details of a tweet from its id.
# Get Twitter Followers
Source: https://docs.memoryproto.co/api-reference/memory-api/endpoints/social-graph/get-twitter-followers
get /twitter/followers
Retrieve the Twitter followers with Farcaster profile links of an account by handle. If the followers aren’t already stored in our system, the request will queue a background job and return a `queued` status. As soon as fetching begins, the status becomes `in_progress`, and partial results are available, use the `progress` field to track completion. Once all followers have been retrieved, the status changes to `completed`. The maximum age of stored followers is 30 days.
# Get Twitter Followers Status
Source: https://docs.memoryproto.co/api-reference/memory-api/endpoints/social-graph/get-twitter-followers-status
get /twitter/followers/status
Check the indexing status of Twitter followers for an account. This endpoint does not trigger a new queue and does not cost credits. Returns 404 if the user has never been queued.
# Get Twitter Following
Source: https://docs.memoryproto.co/api-reference/memory-api/endpoints/social-graph/get-twitter-following
get /twitter/following
Retrieve the Twitter following with Farcaster profile links of an account by handle. If the following aren't already stored in our system, the request will queue a background job and return a `queued` status. As soon as fetching begins, the status becomes `in_progress`, and partial results are available, use the `progress` field to track completion. Once all following have been retrieved, the status changes to `completed`. The maximum age of stored followers is 30 days.
# Get Twitter Following Status
Source: https://docs.memoryproto.co/api-reference/memory-api/endpoints/social-graph/get-twitter-following-status
get /twitter/following/status
Check the indexing status of Twitter following for an account. This endpoint does not trigger a new queue and does not cost credits. Returns 404 if the user has never been queued.
# Get Twitter Posts
Source: https://docs.memoryproto.co/api-reference/memory-api/endpoints/social-graph/get-twitter-posts
get /twitter/posts
Retrieve the Twitter posts of an account by handle. If the posts aren’t already stored in our system, the request will queue a background job and return a `queued` status. As soon as fetching begins, the status becomes `in_progress`, and partial results are available, use the `progress` field to track completion. Once all posts have been retrieved, the status changes to `completed`. The maximum age of stored posts is 30 days.
# Get Twitter profile
Source: https://docs.memoryproto.co/api-reference/memory-api/endpoints/social-graph/get-twitter-profile
get /twitter
Retrieve the Twitter profile with Farcaster linking from a username.
# Get Twitter search results
Source: https://docs.memoryproto.co/api-reference/memory-api/endpoints/social-graph/get-twitter-search
get /twitter/search
Retrieve the Twitter search results for a query.
# Identity Graph
Source: https://docs.memoryproto.co/api-reference/memory-api/identity-graph
Memory Identity Graphs
## Identity Graphs
### What it is
A user identity is made up of different Web2 identities (Twitter, GitHub, website, email) and onchain identities (wallet, Farcaster, Lens). Apps and developers usually only have access to a portion of this data, and querying it across platforms can be complex.
Memory introduces **Identity Graphs**: an array of different user identities from Web2 and Web3 sources that together form a user's online persona. With the Memory API, you can query the identity graph of any user using just a wallet address, ENS, Basename, or a Farcaster, Lens, or Zora username.
### How it works
Identity Graphs are built by querying publicly available links for a user, registering the source of each identity, and connecting them. At the end, you get a comprehensive list of a user's identities along with their sources, making it possible to evaluate and filter out untrustworthy data.
In addition to public sources, the [Memory App](https://app.memoryproto.co/) allows users to curate their own identity graph by adding or removing identity links.
### In practice
Below you can see the whole identity graph of [Jesse Pollak](https://x.com/jessepollak) by querying its main wallet ENS [jesse.xyz](https://etherscan.io/name-lookup-search?id=jesse.xyz).
As you can see we have identities for Ethereum, Farcaster, Twitter, GitHub, Basenames, Talent Protocol, Lens, website and email, all queried from a single ENS name. And each identity node has a `source` field, which describes from which other identities and platforms the link was found. For more information about the available identities, check the [identities section.](/essentials/identities)
```json theme={null}
[
// ...
{
"id": "0x849151d7d0bf1f34b70d5cad5149d28cc2308bf1",
"platform": "ethereum",
"url": "https://etherscan.io/address/0x849151d7d0bf1f34b70d5cad5149d28cc2308bf1",
"avatar": "data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCA4IDgiIHNoYXBlLXJlbmRlcmluZz0ib3B0aW1pemVTcGVlZCIgd2lkdGg9IjY0IiBoZWlnaHQ9IjY0Ij48cGF0aCBmaWxsPSJoc2woOTUgNzMlIDc1JSkiIGQ9Ik0wLDBIOFY4SDB6Ii8+PHBhdGggZmlsbD0iaHNsKDEzMCA5MiUgMjQlKSIgZD0iTTAsMGgxdjFoLTF6TTcsMGgxdjFoLTF6TTMsMGgxdjFoLTF6TTQsMGgxdjFoLTF6TTAsMWgxdjFoLTF6TTcsMWgxdjFoLTF6TTMsMWgxdjFoLTF6TTQsMWgxdjFoLTF6TTEsMmgxdjFoLTF6TTYsMmgxdjFoLTF6TTIsM2gxdjFoLTF6TTUsM2gxdjFoLTF6TTIsNGgxdjFoLTF6TTUsNGgxdjFoLTF6TTMsNGgxdjFoLTF6TTQsNGgxdjFoLTF6TTIsNWgxdjFoLTF6TTUsNWgxdjFoLTF6TTMsNWgxdjFoLTF6TTQsNWgxdjFoLTF6TTAsNmgxdjFoLTF6TTcsNmgxdjFoLTF6TTMsNmgxdjFoLTF6TTQsNmgxdjFoLTF6Ii8+PHBhdGggZmlsbD0iaHNsKDg2IDk3JSA4NSUpIiBkPSJNMiwxaDF2MWgtMXpNNSwxaDF2MWgtMXpNMiwyaDF2MWgtMXpNNSwyaDF2MWgtMXpNMSw0aDF2MWgtMXpNNiw0aDF2MWgtMXpNMiw2aDF2MWgtMXpNNSw2aDF2MWgtMXoiLz48L3N2Zz4=",
"username": null,
"social": null,
"sources": [
{
"id": "99",
"platform": "farcaster",
"verified": true
},
{
"id": "353682",
"platform": "talent-protocol",
"verified": true
}
]
},
{
"id": "99",
"platform": "farcaster",
"url": "https://warpcast.com/jessepollak",
"social": {
"followers": 496387,
"following": 1877,
"verified": null
},
"avatar": "https://imagedelivery.net/BXluQx4ige9GuW0Ia56BHw/1013b0f6-1bf4-4f4e-15fb-34be06fede00/original",
"username": "jessepollak",
"sources": [
{
"id": "99",
"platform": "farcaster",
"verified": true
},
{
"id": "353682",
"platform": "talent-protocol",
"verified": true
}
]
},
{
"id": "1097953",
"username": "jessepollak",
"social": {
"verified": null,
"followers": 1097,
"following": 61
},
"avatar": "https://avatars.githubusercontent.com/u/1097953?v=4",
"url": "https://github.com/jessepollak",
"platform": "github",
"sources": [
{
"id": "353682",
"platform": "talent-protocol",
"verified": true
},
{
"id": "jesse.xyz",
"platform": "ens",
"verified": true
}
]
},
{
"id": "jesse.base.eth",
"social": null,
"avatar": null,
"url": "https://www.base.org/name/jesse.base.eth",
"platform": "basenames",
"username": null,
"sources": [
{
"id": "353682",
"platform": "talent-protocol",
"verified": true
}
]
},
{
"id": "0x4c14105711eccb2c3ade694fc0227e3a5cc4f237",
"avatar": null,
"platform": "lens",
"username": "jessepollak",
"url": "https://hey.xyz/u/jessepollak",
"social": {
"verified": null,
"followers": 150,
"following": 36
},
"sources": [
{
"id": "353682",
"platform": "talent-protocol",
"verified": true
},
{
"id": "0x4c14105711eccb2c3ade694fc0227e3a5cc4f237",
"platform": "lens",
"verified": true
}
]
},
{
"id": "353682",
"avatar": "https://imagedelivery.net/BXluQx4ige9GuW0Ia56BHw/1013b0f6-1bf4-4f4e-15fb-34be06fede00/original",
"platform": "talent-protocol",
"url": "https://app.talentprotocol.com/profile/353682",
"username": null,
"social": null,
"sources": [
{
"id": "353682",
"platform": "talent-protocol",
"verified": true
}
]
},
{
"platform": "ens",
"id": "jesse.xyz",
"url": "https://app.ens.domains/jesse.xyz",
"avatar": "https://s.gravatar.com/avatar/905fd6810cd184a461697d811a319272.jpg",
"username": null,
"social": null,
"sources": [
{
"id": "jesse.xyz",
"platform": "ens",
"verified": true
}
]
},
// ...
]
```
## Linking Identities
Memory Lets API consumers to write back to the identity graph by creating new users links that enhance the identity graph by providing a user verification flow for verified projects. If you want to get verified and contribute to Memory's identity graph see the [Developers Page](https://memoryproto.co/developers)
## Identity Metadata
Each identity node (e.g., Twitter/X, GitHub, ENS) can include optional metadata provided by Memory. This may include, for example, Twitter follower/following stats for each account. Identity metadata will be available soon—stay tuned for updates.
# Introduction
Source: https://docs.memoryproto.co/api-reference/memory-api/introduction
Welcome to the Memory API Reference.
## Overview
Welcome to the **Memory API**. This API lets you retrieve identity graphs from user and public data from Twitter and Farcaster.
## OpenAPI Specification
We use an [OpenAPI (3.1)](https://mintlify.com/docs/api-playground/openapi/setup) file to document the Memory Protocol API. This specification includes endpoint definitions, parameters, request/response examples, and authentication requirements.
**Key details from the spec**:
* **Title**: Memory API (v1.0.0)
* **Description**: Generated from our OpenAPI specification
* **Server**: `https://api.memoryproto.co`
* **Authentication**: Bearer token
To learn more, or to integrate this spec into your own tooling, visit the link below.
View the OpenAPI specification file
## Authentication
All endpoints require a **Bearer token** for authentication. You can register for an API key at the [Memory developer dashboard](https://memoryproto.co/dashboard). Once you have your token:
1. Include it in an `Authorization` header as `Bearer `.
2. Make requests to any of the endpoints documented in our spec.
# Social Graph
Source: https://docs.memoryproto.co/api-reference/memory-api/social-graph
Memory Social Graphs
## Social Graphs
### What it is
Memory allows users to monetize their personal data, either public or private, by uploading it to the protocol and allowing consumer apps to access it by paying a fee in **\$MEM**. With that, consumer apps can create an enriched user experience by tapping into complex public and private data from their users. Part of the fees go to the protocol and the rest goes to the user that provided data.
### How it works
For publicly available data like Twitter and Farcaster follow graphs and posts, the user doesn't need to do any action, Memory's backend automatically indexes data for any user and provides it to consumer apps. Even for public data that doesn't require any action, users are rewarded in part of the protocol fees if they get queried by consumer apps as an onboarding incentive to upload private data.
Consumer applications can access data through the Memory API using either pre-purchased API credits with **\$MEM** tokens or through x402 micropayments for one-off purchases. The Memory Fee Router automatically splits payments between the protocol treasury and data providers, with weekly reward distributions through an on-chain Merkle Tree distributor contract.
# Identities
Source: https://docs.memoryproto.co/essentials/identities
Explore supported identities and platforms.
Memory allows you to retrieve a graph of user identities based on a single identity input. However, not all identities are the same. Memory supports three types:
### Searchable identities
Identities you can use to query the identity graph:
* [Ethereum address](/api-reference/endpoint/get-user-identity-graph-by-wallet)
* [Farcaster](/api-reference/endpoint/get-user-identity-graph-by-farcaster-username)
* [Twitter](/api-reference/endpoint/get-user-identity-graph-by-twitter-username)
* [Lens](/api-reference/endpoint/get-user-identity-graph-by-lens-username)
* [Zora](/api-reference/endpoint/get-user-identity-graph-by-zora-username)
### Source identities
Identities whose platforms can contain links to other identities (e.g., ENS records or Farcaster wallet and Twitter links). Only source identities appear in the `sources` field of the identity graph.
* [Farcaster](https://www.farcaster.xyz/)
* [ENS](https://ens.domains/)
* [Basenames](https://www.base.org/names)
* [GitHub](https://github.com/)
* [Talent Protocol](https://www.talentprotocol.com/)
* [Lens](https://lens.xyz/)
* [Zora](https://zora.co/)
### Core identities
This is the broader group, all the identities that can be returned in the identity graph.
* Ethereum address
* Solana address
* Email
* Website
* [Farcaster](https://www.farcaster.xyz/)
* [ENS](https://ens.domains/)
* [Basenames](https://www.base.org/names)
* [GitHub](https://github.com/)
* [Factory](https://factory.fm/)
* [Talent Protocol](https://www.talentprotocol.com/)
* [Lens](https://lens.xyz/)
* [Zora](https://zora.co/)
#### Support for new identities
Memory is always looking to support new identity types and expand the identity graph. If you're interested in bringing your platform to Memory, reach out to us at [hello@memoryproto.co](mailto:hello@memoryproto.co).
# Token Rewards
Source: https://docs.memoryproto.co/essentials/rewards
Learn about earning Memory rewards.
## How Rewards Work
Memory Protocol rewards users for contributing valuable data to the ecosystem. When consumer applications query your data through the Memory API, you automatically earn a share of the \$MEM tokens they pay. The more frequently your data is accessed, the more you earn.
## Earning Without Effort
Even if you've never used Memory, you're already earning! The protocol automatically indexes public data from platforms like Twitter and Farcaster. Whenever applications query your public social graph or posts, you receive a portion of the fees—no action required. This passive income serves as an incentive to explore deeper engagement with the protocol.
## Reward Distribution
Rewards are calculated and distributed weekly through an on-chain Merkle Tree distributor contract. The system tracks all data queries throughout the week and computes each user's earnings based on:
* Frequency of data access by consumer apps
* Type of data queried (public, structured, or unstructured)
* Overall data quality and completeness
## Payment Flow
When consumer apps access data:
1. Apps pay in \$MEM tokens (via API credits or x402 micropayments)
2. The Memory Fee Router automatically splits payments
3. Your portion accumulates throughout the week
4. Weekly distributions are sent directly to your wallet
## Future Opportunities
As Memory evolves, additional earning opportunities will emerge:
* **Structured Data Rewards**: Upload verified data like ChatGPT histories or Spotify preferences for fixed query fees
* **Curation Rewards**: In later phases, stake \$MEM to validate data quality and earn curation rewards
* **Partner Integrations**: Projects that help users curate their identities will also participate in the reward ecosystem
Stay tuned as we expand the ways you can monetize your digital identity through Memory Protocol.
# Introduction
Source: https://docs.memoryproto.co/introduction
Welcome to Memory Protocol.
Memory makes your digital identity portable across the internet. Followers you gain, content you like, reviews you leave—everything you create online—should move effortlessly with you, no matter which app you're using. It's not about ideology; it's about convenience, better experiences, and reducing friction among the apps you love.
Memory Protocol lets individuals upload both structured and unstructured data and earn a share of the fees that consumer applications pay to access it. Payments are made in **\$MEM**: a portion goes to the protocol treasury, the remainder is routed to the data owners whose information was queried. Because a user's earnings scale with how frequently their data is consumed, contributors are naturally incentivised to submit high-quality, well-described datasets.
## Social Graphs
### What it is
Memory allows users to monetize their personal data, either public or private, by uploading it to the protocol and allowing consumer apps to access it by paying a fee in **\$MEM**. With that, consumer apps can create an enriched user experience by tapping into complex public and private data from their users. Part of the fees go to the protocol and the rest goes to the user that provided data.
### How it works
For publicly available data like Twitter and Farcaster follow graphs and posts, the user doesn't need to do any action, Memory's backend automatically indexes data for any user and provides it to consumer apps. Even for public data that doesn't require any action, users are rewarded in part of the protocol fees if they get queried by consumer apps as an onboarding incentive to upload private data.
Consumer applications can access data through the Memory API using either pre-purchased API credits with **\$MEM** tokens or through x402 micropayments for one-off purchases. The Memory Fee Router automatically splits payments between the protocol treasury and data providers, with weekly reward distributions through an on-chain Merkle Tree distributor contract.
### Uploading private data
There are 2 types of private data: structured and unstructured. Structured data is a set of data defined and validated by Memory, where users can upload and expect a fixed price per query via consumer apps. New structured data options will be rolled out as the protocol evolves, like ChatGPT conversation history, Spotify listening history and more.
The unstructured data market is a more complex setup, where users will be able to upload any kind of data with a valid schema for consumption, and data curators will evaluate the quality and value for it so the price paid by consumer apps is fair when querying it. In the future, curators will stake **\$MEM** to signal data quality, earning rewards for accurate assessments.
## Identity Graphs
### What it is
A user identity is made up of different Web2 identities (Twitter, GitHub, website, email) and onchain identities (wallet, Farcaster, Lens). Apps and developers usually only have access to a portion of this data, and querying it across platforms can be complex.
Memory introduces **Identity Graphs**: an array of different user identities from Web2 and Web3 sources that together form a user's online persona. With the Memory API, you can query the identity graph of any user using just a wallet address, ENS, Basename, or a Farcaster, Lens, or Zora username.
### How it works
Identity Graphs are built by querying publicly available links for a user, registering the source of each identity, and connecting them. At the end, you get a comprehensive list of a user's identities along with their sources, making it possible to evaluate and filter out untrustworthy data.
In addition to public sources, the [Memory App](https://app.memoryproto.co/) allows users to curate their own identity graph by adding or removing identity links.
### In practice
Below you can see the whole identity graph of [Jesse Pollak](https://x.com/jessepollak) by querying its main wallet ENS [jesse.xyz](https://etherscan.io/name-lookup-search?id=jesse.xyz).
As you can see we have identities for Ethereum, Farcaster, Twitter, GitHub, Basenames, Talent Protocol, Lens, website and email, all queried from a single ENS name. And each identity node has a `source` field, which describes from which other identities and platforms the link was found. For more information about the available identities, check the [identities section.](/essentials/identities)
```json theme={null}
[
// ...
{
"id": "0x849151d7d0bf1f34b70d5cad5149d28cc2308bf1",
"platform": "ethereum",
"url": "https://etherscan.io/address/0x849151d7d0bf1f34b70d5cad5149d28cc2308bf1",
"avatar": "data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCA4IDgiIHNoYXBlLXJlbmRlcmluZz0ib3B0aW1pemVTcGVlZCIgd2lkdGg9IjY0IiBoZWlnaHQ9IjY0Ij48cGF0aCBmaWxsPSJoc2woOTUgNzMlIDc1JSkiIGQ9Ik0wLDBIOFY4SDB6Ii8+PHBhdGggZmlsbD0iaHNsKDEzMCA5MiUgMjQlKSIgZD0iTTAsMGgxdjFoLTF6TTcsMGgxdjFoLTF6TTMsMGgxdjFoLTF6TTQsMGgxdjFoLTF6TTAsMWgxdjFoLTF6TTcsMWgxdjFoLTF6TTMsMWgxdjFoLTF6TTQsMWgxdjFoLTF6TTEsMmgxdjFoLTF6TTYsMmgxdjFoLTF6TTIsM2gxdjFoLTF6TTUsM2gxdjFoLTF6TTIsNGgxdjFoLTF6TTUsNGgxdjFoLTF6TTMsNGgxdjFoLTF6TTQsNGgxdjFoLTF6TTIsNWgxdjFoLTF6TTUsNWgxdjFoLTF6TTMsNWgxdjFoLTF6TTQsNWgxdjFoLTF6TTAsNmgxdjFoLTF6TTcsNmgxdjFoLTF6TTMsNmgxdjFoLTF6TTQsNmgxdjFoLTF6Ii8+PHBhdGggZmlsbD0iaHNsKDg2IDk3JSA4NSUpIiBkPSJNMiwxaDF2MWgtMXpNNSwxaDF2MWgtMXpNMiwyaDF2MWgtMXpNNSwyaDF2MWgtMXpNMSw0aDF2MWgtMXpNNiw0aDF2MWgtMXpNMiw2aDF2MWgtMXpNNSw2aDF2MWgtMXoiLz48L3N2Zz4=",
"username": null,
"social": null,
"sources": [
{
"id": "99",
"platform": "farcaster",
"verified": true
},
{
"id": "353682",
"platform": "talent-protocol",
"verified": true
}
]
},
{
"id": "99",
"platform": "farcaster",
"url": "https://warpcast.com/jessepollak",
"social": {
"followers": 496387,
"following": 1877,
"verified": null
},
"avatar": "https://imagedelivery.net/BXluQx4ige9GuW0Ia56BHw/1013b0f6-1bf4-4f4e-15fb-34be06fede00/original",
"username": "jessepollak",
"sources": [
{
"id": "99",
"platform": "farcaster",
"verified": true
},
{
"id": "353682",
"platform": "talent-protocol",
"verified": true
}
]
},
{
"id": "1097953",
"username": "jessepollak",
"social": {
"verified": null,
"followers": 1097,
"following": 61
},
"avatar": "https://avatars.githubusercontent.com/u/1097953?v=4",
"url": "https://github.com/jessepollak",
"platform": "github",
"sources": [
{
"id": "353682",
"platform": "talent-protocol",
"verified": true
},
{
"id": "jesse.xyz",
"platform": "ens",
"verified": true
}
]
},
{
"id": "jesse.base.eth",
"social": null,
"avatar": null,
"url": "https://www.base.org/name/jesse.base.eth",
"platform": "basenames",
"username": null,
"sources": [
{
"id": "353682",
"platform": "talent-protocol",
"verified": true
}
]
},
{
"id": "0x4c14105711eccb2c3ade694fc0227e3a5cc4f237",
"avatar": null,
"platform": "lens",
"username": "jessepollak",
"url": "https://hey.xyz/u/jessepollak",
"social": {
"verified": null,
"followers": 150,
"following": 36
},
"sources": [
{
"id": "353682",
"platform": "talent-protocol",
"verified": true
},
{
"id": "0x4c14105711eccb2c3ade694fc0227e3a5cc4f237",
"platform": "lens",
"verified": true
}
]
},
{
"id": "353682",
"avatar": "https://imagedelivery.net/BXluQx4ige9GuW0Ia56BHw/1013b0f6-1bf4-4f4e-15fb-34be06fede00/original",
"platform": "talent-protocol",
"url": "https://app.talentprotocol.com/profile/353682",
"username": null,
"social": null,
"sources": [
{
"id": "353682",
"platform": "talent-protocol",
"verified": true
}
]
},
{
"platform": "ens",
"id": "jesse.xyz",
"url": "https://app.ens.domains/jesse.xyz",
"avatar": "https://s.gravatar.com/avatar/905fd6810cd184a461697d811a319272.jpg",
"username": null,
"social": null,
"sources": [
{
"id": "jesse.xyz",
"platform": "ens",
"verified": true
}
]
},
// ...
]
```
## Linking Identities
Memory Lets API consumers to write back to the identity graph by creating new users links that enhance the identity graph by providing a user verification flow for verified projects. If you want to get verified and contribute to Memory's identity graph see the [Developers Page](https://memoryproto.co/developers)
## Identity Metadata
Each identity node (e.g., Twitter/X, GitHub, ENS) can include optional metadata provided by Memory. This may include, for example, Twitter follower/following stats for each account. Identity metadata will be available soon—stay tuned for updates.
## Next Steps
Start exploring Memory and see what you can build.
Get started using Memory right away.
Dive deeper into the Memory API.
Explore supported identities and platforms.
Learn about earning Memory rewards.
# Quickstart
Source: https://docs.memoryproto.co/quickstart
Start building with Memory.
## Set Up Your Memory Developer Account
1. **Create an Organization**\
Visit the [Memory developer dashboard](https://memoryproto.co/dashboard) to create an Organization. This step ensures you have a dedicated workspace for managing your projects and settings.
2. **Generate an API Key**\
After creating an Organization, generate an API key. This key is required to authenticate your requests to the Memory API.
## Start Querying Identity Graphs
With your API key in hand, you can now query user identity graphs based on a user’s wallet address or Farcaster account. The Memory API returns connected identities from various platforms, such as Twitter(X), GitHub, ENS, and more.
To learn more about the available endpoints and how to structure your requests, visit the [API Reference](/api-reference/memory-api/introduction).
Dive deeper into the Memory API.