Skip to content

feat(ecosystem): add AI Talent Atlas — researcher intelligence API#168

Open
FuturMix wants to merge 1 commit into
coinbase:mainfrom
FuturMix:feat/add-ai-talent-atlas
Open

feat(ecosystem): add AI Talent Atlas — researcher intelligence API#168
FuturMix wants to merge 1 commit into
coinbase:mainfrom
FuturMix:feat/add-ai-talent-atlas

Conversation

@FuturMix
Copy link
Copy Markdown

Description

Adds AI Talent Atlas to the x402 ecosystem page as a Services/Endpoints provider.

AI Talent Atlas is a pay-per-request data API serving structured intelligence on 643 AI researchers across 14 major labs. Agents and developers can query researcher profiles, organizational charts, talent flow matrices, co-author networks, and departure tracking — all via x402 micropayments.

x402 Integration

  • Website: https://www.agentrift.tech
  • Price range: $0.01–$0.50 USDC per request
  • Network: Base (eip155:8453)
  • Scheme: exact
  • Facilitator: xpay.sh (zero-fee, non-custodial)
  • 8 paid endpoints + 2 free endpoints

Endpoints

Endpoint Price Description
GET /api/v1/researchers $0.01 Search researchers (filters: org, dept, status, chinese, q)
GET /api/v1/researcher/:id $0.02 Full researcher profile
GET /api/v1/org/:name $0.03 Organization chart + all researchers
GET /api/v1/talent-flow $0.05 Talent flow matrix (148 movements)
GET /api/v1/coauthors/:name $0.03 Cross-org co-author network
GET /api/v1/departures $0.02 Departure tracking
GET /api/v1/chinese-talent $0.03 Chinese AI researchers across all labs
POST /api/v1/bulk-export $0.50 Full CSV/JSON export

Data Coverage

  • 643 researchers across 14 organizations: OpenAI, Anthropic, DeepMind, Meta, Microsoft, xAI, ByteDance, Alibaba, Baidu, Tencent, Apple, Mistral, Amazon, DeepSeek
  • h-index and citation data (Semantic Scholar + DBLP)
  • Contact information (X, LinkedIn, personal websites)
  • 3,492 cross-org co-author pairs
  • 148 talent flow movements

Files

  • typescript/site/app/ecosystem/partners-data/ai-talent-atlas/metadata.json
  • typescript/site/public/logos/ai-talent-atlas.png (512x512 PNG)

Category

Services/Endpoints, with typeLabel: "Data".

Tests

  • Verified metadata.json parses as valid JSON
  • Logo is 512x512 PNG

AI tools were used in preparing this submission.

AI Talent Atlas is a pay-per-request data API serving structured
intelligence on 643 AI researchers across 14 major labs (OpenAI,
Anthropic, DeepMind, Meta, etc.). Endpoints include researcher search,
org charts, talent flow matrix, co-author networks, and departure
tracking. Payments via x402 exact scheme, USDC on Base.
@cb-heimdall
Copy link
Copy Markdown

🟡 Heimdall Review Status

Requirement Status More Info
Reviews 🟡 0/1
Denominator calculation
Show calculation
1 if user is bot 0
1 if user is external 0
2 if repo is sensitive 0
From .codeflow.yml 1
Additional review requirements
Show calculation
Max 0
0
From CODEOWNERS 0
Global minimum 0
Max 1
1
1 if commit is unverified 1
Sum 2

@TateLyman
Copy link
Copy Markdown

Quick no-payment discovery check on the submitted site. No payment headers, signatures, wallet, API key, or paid calls.

Repro:

npx --yes x402-surface-check@latest https://www.agentrift.tech --limit 8 --origin https://www.agentrift.tech
for p in /.well-known/x402 /.well-known/agent.json /openapi.json /api/openapi.json /llms.txt; do curl -i https://www.agentrift.tech | head; done

Observed: the public page is reachable, but the common machine-readable discovery paths I checked all return the HTML landing page rather than JSON/OpenAPI/llms text. If this listing is only meant to point humans at a product page, that may be fine. If it is meant to be discoverable by agents from the x402 ecosystem directory, I would add at least one canonical machine-readable entrypoint, for example:

  • /.well-known/x402 or /.well-known/agent.json with paid endpoint URLs, methods, prices, network, asset, and facilitator.
  • /openapi.json with the paid routes and 402 response shape.
  • /llms.txt with a short agent-readable capability description and the discovery URL.

That would make it easier for agents and registry scanners to verify the paid API surface without guessing from the HTML page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

3 participants