FetchTalos HUB

not connected

Overview

GET /v1/hub/stats — your own activity only

TALENTS IN ROSTER
ACTIVE CONTRACTS
ENTERPRISES ENGAGED
PAYMENTS SETTLED
TOTAL SALARY PAID (₦)
YOUR MARKUP EARNED (₦)

My Talents

Your own roster — upload new talent (bulk or one at a time), or edit anyone already here

Add a talent

Bulk upload

One talent per line: name, email, country, vetted_score, stack1|stack2. Country and score are optional (defaults to NG / 75). Re-uploading an email already in YOUR roster updates it instead of duplicating.

NameEmailStackCountryScoreStatusActions
// connect to load

Markup & Settlement Account

Your white-label revenue share on top of FetchTalos's own platform fee, paid to your own account every time a talent under your pipeline gets paid

Your markup rate

Ceiling set by FetchTalos: . You can set your own rate anywhere up to that.

Where your markup gets paid

Payment notifications

Every time a talent under your pipeline gets paid, we'll email this address how much they received and how much of your markup was settled to you. Without this set, you won't be notified at all.

Plans

GET /v1/plans — real benefits and pricing, straight from the live catalog

// connect to load

Estimate a total

What an enterprise would actually owe — salary + FetchTalos's fee + your markup, plus insurance whenever it's due for renewal (which depends on the coverage duration chosen, not always just month one).

Simulate an Enterprise

Walk through exactly what an enterprise partnering with YOUR hub would experience — real API calls, under your own pipeline and markup. Doubles as your own sandbox to verify your setup once you're live.

Engage a talent from your roster

GET /v1/engagements — every engagement you've sent, real and persisted. Refreshing the page never loses this; it's not held in browser memory.

TalentInterview linkStatusAction
// connect to load

GET /v1/contracts — same idea. Once a talent accepts a contract, the full amount due and where to send it show up here directly — no need to click anything to see it. "Simulate: transfer received" is a testing tool for what happens AFTER a real bank transfer lands, not how you'd see the payment details.

// connect to load