Get curator details
Resolve curator details using the selector <chain_id>:<curator_address>, where the address is the vault's on-chain curator role. This joins directly from Core Vault V1 and V2 responses, which remain unchanged and expose the address only.
name, logo_uri, and socials are editorial metadata from Morpho's curator registry, morpho-org/morpho-blue-api-metadata/data/curators-listing.json, not on-chain facts. This is an explicit exception to Core's facts-only rule. The registry syncs about every five minutes, lookups are cached for up to five minutes, and responses may be CDN-cached for up to five minutes, so a registry change can take up to about fifteen minutes to appear.
Results are every curator registry profile registered to the supplied chain and address. They are registry matches, not a verified or vault-scoped attribution: they can include unverified profiles and owner-only profiles, which the response does not distinguish. GraphQL Vault.state.curators / VaultV2.curators resolve curators per vault instead: they return none unless the vault was ever listed and its owner address has a registry profile, combine the owner's and curator's profiles, drop owner-only profiles, and fall back to the underlying V1 vault for a V2 fee wrapper. This route alone does not reproduce those vault-scoped results.
A 404 means the selected chain is unsupported or not exposed by Core.
Path Parameters
Selector formatted as <chain_id>:<curator_address>. Example: 1:0x827e86072B06674a077f592A531dcE4590aDeCdB.
<chain_id>:<curator_address>Response Body
application/json
curl -X GET "https://example.com/v0/curators/1:0x827e86072B06674a077f592A531dcE4590aDeCdB/details"{ "data": { "chain_id": 1, "curator_address": "0x827e86072B06674a077f592A531dcE4590aDeCdB", "curators": [ { "id": "steakhouse-financial", "logo_uri": "https://cdn.morpho.org/v2/assets/images/steakhouse.svg", "name": "Steakhouse Financial", "socials": [ { "type": "url", "url": "https://www.steakhouse.financial" } ] } ] }}