The JSON blob below represents the "response" from our API.

The user provides us with an `address`, in this case "0xc75446a6adaef73269dbdece73536977b2b639e0", and receives **context** about that address; interests, affiliations, identities.

This data enriches their internal tools, i/e customer|community relationship management tools with context.

{
	
	"address": "0xc75446a6adaef73269dbdece73536977b2b639e0",
	"chainverseLabels": [
		"DAO Contributor",
		"Gitcoin Grants Donor",
		"Web3 Developer",
		"Prop House Winner",
		"Music NFT Collector",
		"Under-represented Minority Article Author"
	],
	"socialMedia": [
		{
			"platform": "Twitter",
			"handle": "amphib0ly"
		},
		{
			"platform": "Github",
			"handle": "amphibiousmaximus"
		},
		{
			"platform": "Farcaster",
			"handle": "amphiboly",
		},
		{
			"platform": "Sound XYZ",
			"handle": "iamjordanolmstead",
			"link": "https://www.sound.xyz/iamjordanolmstead"
		}
	],
	"affiliations": [
		{
			"name": "Diamond DAO",
			"contractAddresses": [
				"0xc8red989fd9d98f9df89ddfdd"
			],
			"twitter": "https://twitter.com/dmnddao"
			"firstActive": "2021-07-28"
		},
		{
			"name": "Lil Nouns",
			"contractAddresses":  [
			"0xfd9r8fd9f89df8d9f8d9afaa"
			],
			"twitter": "https://twitter.com/lilnounsdao"
		}

	]
}

What I would like to illustrate is how this sort of data can **enrich** data that a user already has to help them make better decisions.

To that end, it would be great to have a table with three or four columns, i/e address, # NFTs held, ETH held, something that demonstrates the response from the API (which is above), and then the simple table view being enriched with additional columns taken from the JSON (i.e. social accounts, affiliations, chainverse labels)

i,e this boring table as without chainverse

and then a cooler looking table with more columns, that have values taken from the JSON above, as the better, more context-aware experience w/Chainverse