Talent Powers

Query professioanl data from Talent Protocol – a platform that tracks builders

Use this skill to:

• Find verified developers by location, skills, or identity (Twitter/GitHub/Farcaster/wallet)
• Check builder reputation (ranks by default, scores only when asked)
• Map Twitter accounts with Wallet addresses
• Verify human identity from a wallet
• Search for builder’s credentials (earnings, contributions, hackathons, contracts, etc)
• Check the projects each builder is shipping

First get your API Key: API Key: https://talent.app/~/settings/api
Base URL: https://api.talentprotocol.com

curl -H "X-API-KEY: $TALENT_API_KEY" "https://api.talentprotocol.com/..."

Endpoints

Key Parameters

Identity lookup:

query[identity]={handle}&query[identity_type]={twitter|github|farcaster|ens|wallet}

Filters (all optional, only use when relevant to the query):

query[tags][]=developer              # filter by tag (developer, designer, etc.)
query[verified_nationality]=true     # only verified nationality
query[human_checkmark]=true          # only human-verified (reduces results significantly)

Sorting:

sort[score][order]=desc&sort[score][scorer]=Builder%20Score

Pagination: page=1&per_page=250 (max 250)

URL Encoding

[ = %5B, ] = %5D, Space = %20

Response Fields

Default → Ranks (always use unless user asks for scores):

• builder_score.rank_position – Primary rank metric
• scores[].rank_position where slug = "builder_score" – Latest rank

Only when user explicitly asks for scores:

• builder_score.points – Score value

• scores[].points – Individual score values

• location – User-entered location (returned in response)

Location Filter

DO NOT USE query[standardized_location]=Country – doesn’t work.

USE customQuery with regex:

curl -X POST -H "X-API-KEY: $TALENT_API_KEY" -H "Content-Type: application/json" \
  "https://api.talentprotocol.com/search/advanced/profiles" \
  -d '{
    "customQuery": {
      "regexp": {
        "standardized_location": {
          "value": ".*argentina.*",
          "case_insensitive": true
        }
      }
    },
    "sort": { "score": { "order": "desc", "scorer": "Builder Score" } },
    "perPage": 50
  }'

See use-cases.md for more examples.

Limitations

• Max 250 per page
• GET only for most endpoints (POST for customQuery)
• Simple query[standardized_location] param broken – use customQuery regex

GitHub Enrichment

Get projects/repos via GitHub after resolving username from /accounts:

# 1. Get GitHub username
/accounts?id={profile_id} → { "source": "github", "username": "..." }

# 2. Query GitHub
GET https://api.github.com/users/{username}                           # Profile
GET https://api.github.com/users/{username}/repos?sort=stars&per_page=5   # Top repos
GET https://api.github.com/users/{username}/repos?sort=pushed&per_page=5  # Recent
GET https://api.github.com/users/{username}/events/public             # Commits
GET https://api.github.com/search/issues?q=author:{username}+type:pr+state:open  # Open PRs

GitHub Token (recommended): Without a token, GitHub limits to 60 requests/hr. With a personal access token, you get 5,000/hr.

• Create one at: https://github.com/settings/tokens → “Generate new token (classic)” → no scopes needed for public data
• Use it: -H "Authorization: token $GITHUB_TOKEN"

References

• endpoints.md – Full endpoint docs
• use-cases.md – Common patterns
• github-enrichment.md – GitHub data