Whitepaper
Maiev
The social layer for builders.
Our thesis
AI can now write a CV, a cover letter, a portfolio and interview answers at almost no cost. When claims are cheap to produce, they stop being useful for hiring decisions.
The signals that remain useful are the ones that are expensive to fake.
Maiev uses two of them:
- Proof of work. Code that has been merged into real projects, reviewed and used by others, and is public for anyone to inspect.
- Proof from peers. Confirmation from people who worked with you, who have their own work and reputation on the record.
Titles, keywords, self-written summaries and endorsements from strangers can be produced on demand. Shipped work and the word of colleagues cannot.
As more code is written with AI, the ability to direct, review and take responsibility for work becomes a more important signal, so Maiev counts reviewed, merged work above unreviewed work.
Proof of work is the foundation, proof from peers adds to it, and the formula that combines them is public.
For builders: a public, ranked record of your work, and roles sent to you with the salary stated.
- A public leaderboard for each skill, ranked from your code and work history.
- Hearts and validations from colleagues and peers, recorded against your skills, your work and each role you held.
- Roles sent to you directly by verified teams, with salary and location stated. No applications.
- $1 for each hunt you answer within 3 days, whether you accept or decline.
- Every open Web3 role in one feed, and a public salary index.
- Only verified teams can contact you, and only while you are open to offers.
For companies and recruiters: contact the top-ranked contributors in the skills you need, directly.
- $3 per hunt from prepaid credit. Maiev takes no placement fee and no share of salary.
- Search the leaderboards, including Rising Stars: the contributors climbing fastest.
- Ranks based on public work and colleague validations, with the formula published.
- A responsiveness score for each contributor, so you know who replies.
- No CVs, and the same tools for in-house teams, recruitment agencies and independent recruiters.
01The problem
Most hiring still runs on applications and self-reported profiles. Recent tools have increased the volume of both without improving the signal.
- Too many applications. One posting can draw hundreds of applications, many of them generated automatically. Strong candidates are hard to find, and screening takes weeks.
- Automation without signal. Automated screening, one-way video interviews and AI transcription process more applications, but tell a company little more about the person.
- Low-signal professional networks. The largest networks reward posting volume. One-click endorsements carry no information, and the work itself is rarely visible.
- Unverifiable claims. CVs and profiles are self-reported. Titles, dates and skills are often inflated, and checking them takes days of reference calls.
- Slow, manual sourcing. Finding strong candidates and checking their claims takes hours of searching and reference calls, for in-house teams and agencies alike.
- Stale availability. “Open to work” flags are set once and rarely updated, so outreach often goes unanswered.
- Web3 specifics. Hiring often happens in direct messages, between pseudonymous accounts, based on claims that can’t be checked.
How Maiev addresses each one
| Problem | What Maiev does |
|---|---|
| Too many applications | Companies send a role to one contributor at a time (a hunt). There is no application queue. 07 |
| Automation without signal | Ranks come from public code and colleague validations. The formula is published, and every score shows how it was built. 05 |
| Low-signal networks | Followers and likes on posts never affect rank. Hearts and validations are weighted by the giver’s own record, and updates are limited to 145 characters. 06 |
| Unverifiable claims | Code is read from public repositories. A role can only be validated by someone who worked at the same company at the same time. Hiring accounts verify their domain. 04 |
| Slow, manual sourcing | Search ranked contributors with verified work and send a hunt from prepaid credit. Maiev takes no placement fee and no share of salary, whether you hire in-house or for clients. 07 |
| Stale availability | Only contributors set to Open can be hunted, and each shows a responsiveness score based on how reliably they answer. 07 |
| Web3 specifics | Handles are supported, but every rank links to public work, and every company or recruiter is verified before it can contact anyone. 08 |
02What Maiev is
Maiev replaces the CV with a public, verifiable profile, and replaces cold outreach with direct, priced contact from verified teams.
- Jobs feed. Open engineering, security, AI, product, design, QA, marketing, business development, trading and operations roles, collected from companies’ public job boards regularly, plus roles posted on Maiev (section 03).
- Profile and work history. Your skills, the public repositories you’ve worked on and the roles you’ve held, each with the hearts and validations it has received.
- Skill leaderboards. 210 skill boards across ten areas (development, security, AI and data, product, design, quality assurance, marketing, BD and sales, trading and operations), 10 ecosystem boards such as Ethereum, Solana and ZK, and a board for each major protocol. Each board can be viewed worldwide or by region, and all time or as Rising Stars: the contributors climbing fastest this year.
- Hearts. Public appreciation for a skill, a piece of work or the time someone spent in a role. Any signed-in member can give them.
- Validations. Confirmation from someone who worked with you that you have a skill or held a role. Only people who worked at the same company at the same time can validate a role. Validations carry the most weight in proof from peers.
- Hunts. A verified company or recruiter sends one role to one contributor, with salary and location stated. If the contributor is interested, a private chat opens.
- Responsiveness score. A score from 0 to 100 for contributors open to offers, based on how reliably they open and answer hunts.
- Bounty board. Verified teams post paid tasks for verified builders, and verified members post roles for verified recruiters to fill. Bids are sealed until bidding closes. Maiev does not hold or move the money (section 08).
- Salary index. Median advertised salaries by area, skill, seniority and region, calculated from live listings and updated regularly at app.maiev.xyz/salaries.
- News and updates. Headlines from the blogs, research forums, security firms and release pages builders read, plus builder stories from crypto newsrooms, with no price talk. Members vote each story useful or not worth it; votes from ranked and verified builders count for more, and the share who found a story useful shows once three have voted. “Built by” names the ranked builders whose public code is in the project a story is about, verified members first. This week’s top stories are public at app.maiev.xyz/news. Members also post short updates of up to 145 characters about what they shipped, fixed or learned.
03Day one: every Web3 job, and your rank in seconds
Maiev has to be useful before any company joins. Two features make it useful on the first visit.
Every Web3 job in one place
Maiev brings open roles from Web3 teams into one feed, alongside roles posted directly on Maiev, and keeps it current through the day. Duplicate listings are merged, closed roles drop off, and new teams appear as they start hiring.
- Filters. Filter by skill, area, remote and minimum salary. Each listing shows the salary (or “Not listed”), the location, the skills it matches and its source.
- A page for every role. Each listing has a public page with the full description. Pages by skill, area, region and company (such as Solidity jobs or remote Web3 jobs) show how many roles are open, the share that are remote and the median advertised salary.
- Apply on the company’s site. Listed roles link to the company’s own application page. Maiev never applies on anyone’s behalf.
- Credit to the source. Every listing names its source and links back to it. A company can claim its listings by verifying its domain, or ask for them to be removed.
Your rank in seconds
When you sign in with GitHub, Maiev reads the public repositories you own and the projects where your pull requests were merged, and ranks you in each skill straight away. Only public work is read, and Maiev never asks for access to private repositories. You can also sign in with Google or X, and connect all three to one account.
- Labelled as estimates. A rank shows as “~#68” with an Estimated tag until a colleague validates the work.
- One formula for everyone. Each repository counts by your steady effort there (with diminishing returns, so volume alone doesn’t win), the project’s value (its stars, the projects that depend on it and the value it secures) and the languages you used. Recent work counts most. The full formula is in section 05.
- Populated leaderboards. The boards start with contributors to the public repositories of more than 200 crypto projects, shown by their GitHub name and avatar, and security researchers ranked from public Code4rena and Immunefi results. They grow as people sign in. Nobody listed this way can be contacted until they sign in, claim their profile and switch on Open to job offers, and anyone can remove their listing.
- Sharing. A rank card can be posted to X. It shows your strongest rank, worldwide or local (for example, #3 in Rust in Sydney), and links to your profile. A live rank badge can be added to a GitHub README.
04Work history
No CV is needed. Add your current and previous roles: company, title, dates, location and the skills you used. Roles appear on your profile next to your skill ranks, and you can edit or remove them at any time.
Hearts for time in a role
Any signed-in member can heart a role on someone’s profile, to acknowledge the time they spent building there.
Validated by colleagues
Only people who worked at the same company at the same time can validate a role: their own work history has to include that company, with overlapping dates. Each role shows how many colleagues validated it, so a role someone typed in looks different from one their team confirmed. To ask a specific colleague, send them a validation link. Each link works once and lasts 30 days, and you can send up to 25 a week. Domain-verified companies will also be able to confirm roles.
Hidden from your current employer
Adding your current role automatically hides your profile from that company’s accounts. See section 09.
05Skill scores and leaderboards
Every contributor gets a score from 0 to 1,000 in each skill. It has two parts: proof of work, read from public code, and proof from peers, the hearts and validations other people give. Proof of work is the foundation: peers can raise a score, but cannot replace shipped work. The formula is public and the same for everyone.
Points have diminishing returns, so contributors at the top of each board remain distinguishable. Product, design and QA skills have no code to read. For those skills, work history replaces code (see below), proof from peers is not capped, and the scale constant is 1,500.
Proof of work
Every public repository someone has worked on adds points to the languages they used there.
| Part | How it’s measured |
|---|---|
| Effort | Each week with commits counts up to 10 commits, so steady work counts and splitting one change into many commits doesn’t. Older work fades with a 24-month half-life. |
| Value | 1 + 0.3 × log(stars) + 0.25 × log(projects that depend on it) + 0.2 × log($M secured by the protocol), up to 4. Dependents come from ecosyste.ms and value secured from DefiLlama. |
| Weight | 1 for code, whether or not the project is crypto. 0.4 for websites, docs, examples and tutorials. |
| Review | 1 for work merged into someone else’s project, where it was reviewed. 0.8 for work in your own repositories. |
| Languages | Points go to the repository’s languages by their share of the code. For members, the languages of the files they actually changed. A language becomes a skill after 10 or more commits in projects where it is at least a quarter of the code. |
Experience (product, design and QA)
With no code to read, these skills start from work history, so people rank as soon as they add the skill. Experience puts someone on the board; hearts and validations move them up it.
| Part | How it’s measured |
|---|---|
| Relevance | 1 if the role is tagged with the skill, 0.85 if the title matches the skill (a Product Manager for Product management), 0.6 if it’s in the same field, 0.15 for any other role. |
| Confidence | 1 once someone has validated the role, 0.75 before. |
| Recency | Halved for every 6 years since the role ended. |
| Experienced years | Each month counts once, at its most relevant role, so overlapping roles don’t add up. At most 15 years. With no dated roles, the years of experience on a profile count at 0.15. |
Fully relevant, validated experience scores about 220 for one year, 400 for five and 585 for fifteen. Experience alone cannot reach the top of a board.
Proof from peers
A heart is appreciation for someone’s work in a skill. A validation comes only from someone who worked with them, at the same company at the same time. Both are weighted by who gives them.
| Part | How it’s measured |
|---|---|
| Giver credibility | trust × (0.35 + 0.65 × the giver’s own score in that skill, or half their best score, ÷ 1,000). Trust is 1 for a verified member or someone with real code on GitHub, 0.6 for an account over 30 days old, and 0.3 for a newer one. Because credibility depends on scores, it is calculated in rounds starting from code, so trust flows from proven work. |
| Each heart | The giver’s credibility. Halved if you heart each other, and a quarter inside a closed ring. |
| Each validation | 0.5 + 0.5 × the giver’s credibility, times how long you worked together (2 or more years counts fully, with a minimum of half). A new account’s validations start at 15% and reach full weight when the account is 7 days old (immediately for verified members and people with real code on GitHub). One person can receive at most 10 validations for the same skill or role per day. |
| Diminishing returns | The square roots mean the first few people count most: four credible hearts count about twice as much as one. |
| Recency | Hearts and validations fade with a 24-month half-life. |
| Cap | For code skills, proof from peers adds at most two-thirds of the proof-of-work points (or 150 points, whichever is more), so it can make up about 40% of a score at most. |
Each score shows how it was built. It is marked Estimated until a colleague validates it, then Validated. The top three on each board are #1 Legend, #2 Champion and #3 Vanguard. Rising Stars are the contributors climbing a skill’s board fastest. The weights are calibrated by checking that widely recognised contributors rank near the top, and any change to the formula is published here.
06Keeping ranks honest
Hearts and validations are easy to give, so the formula limits, weights and checks them.
- Sign-in and daily limits. Hearts and validations require a GitHub, Google or X sign-in. Nobody can heart or validate themselves. Each person can give up to 100 hearts and 20 validations a day, and at most 20 hearts to any one person.
- Weighted givers. A heart from someone with proven code in that skill counts several times as much as one from a new account.
- Reciprocity discount. Hearts between two people who heart each other count at half weight.
- Ring detection. Groups of three or more who all heart each other, with little code evidence between them, count at a quarter.
- Peers can’t replace code. For code skills, proof from peers is capped relative to proof of work.
- Copies count once. Repositories that carry another project’s history (forks of go-ethereum, for example) only credit that work once.
- Followers don’t affect rank. Followers and likes on posts are social features only. They never change skill scores, so an audience cannot be bought to raise a rank.
07Hunts and the responsiveness score
A hunt is one role sent to one contributor: title, salary band, location and a short pitch. It costs $3 USD. If the contributor answers within 3 days, whether “I’m interested” or “Not now”, $1 of the $3 goes to them. Earnings are paid in USDC on Solana on the 1st of each month, once they have cleared for 30 days and the balance is at least $20. Paying contributors to answer means companies get replies.
- Once a hunt is opened, its cost is spent, whatever the answer.
- Only contributors who are open to job offers can be hunted. Their current employer and companies they’ve hidden from can never hunt them, and each company can hunt the same person once every 30 days.
- Credit is bought in packs of $50 (16 hunts) or $250 (83 hunts), by card through Stripe or in USDC on Solana. Unused credit stays on the account. A top-up includes Maiev verification for the person who buys it, at no extra cost.
Contributors open to job offers show a responsiveness score once they have received two or more hunts in the last 180 days:
“Not now” counts as a full answer, so declining is rewarded the same as accepting. Companies see the score next to each contributor in search. It never hides a profile.
08Companies and recruiters
The hiring side works for a single recruiter and for a large in-house team. During setup, an account states who it hires for:
- Your own company. Prove you control the company’s domain, with a DNS record or a code sent to an address at that domain. Free email domains are not accepted. Invite any number of teammates by single-use link. Admins can make other admins, and every hunt shows which teammate sent it.
- Clients, as a recruitment agency. Verify the agency’s own domain and invite as many recruiters as you need. Name the client on a hunt or role, or leave it blank to show “Confidential client”.
- Clients, as an independent recruiter. No company domain is needed. An independent recruiter’s first credit top-up includes Maiev verification, which verifies the account. Independent accounts have one member.
Contributors always see who is contacting them: the verified domain, or “Verified recruiter” for an independent, and the client when it is named. DNS-verified domains are re-checked every 30 days, and email-verified ones every 180 days. A recruiter can never hunt someone on behalf of the client they already work at.
Teammates share one credit balance. Verified accounts can search contributors who are open to offers, send hunts, chat, and post roles that only verified members can apply to. Inviting an applicant to chat uses no credit. Verified employers and agencies get a public team page. Every chat shows a permanent warning to be careful with links and never to share passwords, keys, seed phrases or payment details. Messages are plain text, so links in them aren’t clickable. Members can report an account in one tap, and several reports pause it for review.
Bounty board
The bounty board is for verified members. There are two kinds of bounty:
- Tasks. A verified team posts a piece of work with a budget, and verified builders bid on it.
- Roles. A verified member or team posts a role they need filled, and verified agencies and independent recruiters bid on it.
Budgets range from $50 to $250,000, and bidding stays open for 1 to 14 days. Bids are sealed: each bidder sees only their own, and the poster sees all bids once bidding closes. The poster chooses one bid, not necessarily the lowest, and Maiev opens a private chat between the two. Maiev does not hold or move the money. The two parties agree terms and pay each other directly.
09Privacy and control
Contributors decide who sees what, and can change these settings at any time.
- Open or Closed. Open means verified teams can find you and send you hunts. Closed removes you from search and hunts. Your skill ranks stay public and you stay on the leaderboards.
- Hidden from your current employer. Maiev automatically hides you from your current employer’s domain-verified accounts, so they can’t find, hunt or view you on Maiev. On leaderboards they see “Hidden contributor”.
- How you appear. Show a Git username, an X handle, a first name or the name on your profile. Scores and work history attach to whichever you choose. Nobody has to share their full name, and Maiev never asks for a phone number.
- Leaving the leaderboards. Anyone listed from public GitHub work can remove themselves with one click after signing in, and list themselves again later.
- Your data. Your profile and work history are stored in Maiev’s database. You can edit them at any time, and Maiev deletes them on request.
- Verified contributors. Verification is a one-time $29 USD fee with no subscription, paid through Stripe, or included with a hunt credit top-up of $50 or more. The badge is added as soon as the payment completes, and there is no ID check. Verification adds:
- a verified badge on the leaderboards, the News feed, your public page and your rank card;
- higher placement for your posts in the News feed;
- profile insights: how many people view your profile, where they found you and for which skills, but never who;
- full weight for the hearts and validations you give, since every verified account is a paid one;
- first placement in company search, the ability to apply to roles posted on Maiev, to use the bounty board, and to hide your profile from specific companies.
10Roadmap
| Phase | What happens |
|---|---|
| 1 · Validation | Done. Clickable prototype, interviews with builders and companies, landing page and whitepaper published. |
| 2 · Early access | Live now at app.maiev.xyz: the jobs feed with a page for every role, the salary index, sign-in with GitHub, Google or X, leaderboards of real contributors, profiles with work history, hearts, validations and validation links, news and short updates, verification, the bounty board, and hiring accounts for companies, agencies and independent recruiters. AI assistants can search jobs, leaderboards and salaries through Maiev’s public agent endpoint. Next: companies confirming their own teams’ roles, and agents acting for signed-in members. |
| 3 · Public launch | Open sign-ups, company accounts for every team, and public leaderboards and News feed. |
| 4 · Expansion | Native apps, new skill areas (chains and ecosystems, DeFi, ZK, infrastructure) and more markets. |
11Frequently asked questions
What is Maiev?
Maiev is the social layer for builders. Builders are ranked by the work they’ve shipped and validated by the people they worked with, and verified companies contact them directly with the salary stated. There are no CVs and no applications.
Who is Maiev for?
Web3 builders, starting with smart contract and protocol engineers, security researchers and auditors, AI engineers building onchain, product and project managers, designers and QA engineers, and the Web3 companies that hire them.
How is Maiev different from LinkedIn?
LinkedIn profiles and endorsements are self-reported, and applying means competing with hundreds of other applicants. On Maiev, ranks come from public code and from validations by people who worked with you, using a published formula. Companies contact contributors directly with the salary and location stated. Followers and post likes never affect rank.
How does Maiev rank contributors?
Each contributor gets a score from 0 to 1,000 in every skill, from proof of work and proof from peers. Proof of work comes from public code: steady effort in each repository (up to 10 commits a week, fading with a 24-month half-life), multiplied by the project’s value (stars, dependent projects and value secured) and split across its languages. Proof from peers is hearts and colleague validations, weighted by the giver’s credibility, with diminishing returns, and capped for code skills so peers can raise a score but not replace shipped work. Score = 1000 × (1 − e^(−(work + peers) / 6,000)). The full formula is in the whitepaper. The top three on each board are named Legend, Champion and Vanguard.
Which skills have leaderboards?
210 skill leaderboards across ten areas: development (43, including Solidity, Rust, Move and TypeScript), security (33), AI and data (28), product (13, including product management, project management and product strategy), design (17, including UX, UI and product design), quality assurance (15, including test automation and smart contract testing), marketing (18), BD and sales (14), trading (14) and operations (15). There are also 10 ecosystem boards (Ethereum, Layer 2s, Solana, Bitcoin, Cosmos, Polkadot, Starknet, Aptos & Sui, ZK and DeFi) and a board for each major protocol, such as Uniswap, Aave, Optimism and Jito. Each board can be viewed worldwide or by region.
Can I see my rank before anyone validates me?
Yes. Sign in with GitHub and Maiev reads your public repositories and merged pull requests in a few seconds, then shows your highest-ranked skill, such as top 10% for Rust, with your next three skills below it. Those skills pre-fill your profile. Ranks are labelled Estimated until colleagues validate your work.
Does Maiev access my private GitHub repositories?
No. Maiev only reads public work and never asks for access to private repositories, so your code and your employer’s code stay private. GitHub sign-in requests read-only access to your public profile and email address.
Can I sign in without GitHub?
Yes. Sign in with GitHub, Google or X, and connect the others to the same account later. Only GitHub adds a rank from your public code; Google and X start you with a blank profile. Maiev never asks for a phone number, and a first name or a handle is enough.
Can colleagues validate my work history?
Yes. People who worked at the same company at the same time can validate a role, as long as that role is in their own work history. You can send a specific colleague a one-time validation link, which lasts 30 days. Any signed-in member can also heart a role. Your profile shows how many colleagues validated each role.
Where do the jobs on Maiev come from?
From Web3 teams’ public job boards, refreshed regularly, plus roles posted directly on Maiev. Each listing links to the company’s own application page.
Why is my GitHub profile on Maiev’s leaderboards?
Maiev’s leaderboards start with people who have contributed to the public repositories of the crypto projects it tracks, using only public GitHub data: your GitHub name, avatar, public location and commits. Companies can’t contact you through Maiev unless you sign in, claim the profile and switch on Open to job offers. Sign in with GitHub to claim your profile, or to remove your listing at any time.
Where do the security rankings come from?
The Competitive auditing and Bug bounty hunting boards also rank researchers from public results on Code4rena (High and Medium findings) and Immunefi (its public leaderboard), refreshed daily. Researchers appear under their handle on that platform, with a link to their public profile, and can’t be contacted through Maiev unless they join.
Can my current employer see that I’m open to work?
No. Maiev automatically hides you from your current employer’s domain-verified accounts, so they can’t find, hunt or view you on Maiev. You can also switch to Closed at any time to leave search and hunts.
How do companies contact contributors on Maiev?
With hunts: one role sent to one contributor, with title, salary band, location and a short pitch. A hunt costs $3 USD. If the contributor doesn’t open it within 3 days, 25% is refunded to the company’s credit. If the contributor answers within 3 days, they receive $1. If they are interested, a private chat opens with the company’s team.
How much does hiring on Maiev cost?
A hunt costs $3 USD from prepaid credit, bought in packs of $50 or $250, with 25% back if the contributor doesn’t open it within 3 days. Setting up an account, searching and posting roles are free. Maiev takes no placement fee and no percentage of salary, so agencies keep their own fee arrangements with their clients.
Is Maiev free?
Yes, for builders: signing in, your rank, your profile and work history, the jobs feed, the salary index, hearts and validations are free. Builders also earn $1 for each hunt they answer within 3 days. Verification is optional and costs a one-time $29 USD. Companies pay $3 per hunt from prepaid credit.
How do I get verified on Maiev?
Verification is a one-time $29 USD payment through Stripe, with no subscription. The badge is added as soon as the payment completes, and there is no ID check. Buying $50 or more of hunt credit includes verification.
What’s included in verification?
Verified members get:
- A badge on the leaderboards, the News feed, your public page and your rank card.
- Posts highlighted, and kept near the top of the News feed for longer.
- Profile insights: views each week, where people found you, and for which skills.
- Full weight for the hearts and validations you give, in everyone’s scores.
- First place under Built by on news about projects you’ve contributed to.
- First place in company search.
- Applying to roles posted on Maiev.
- Hiding your profile from specific companies.
- Bidding on bounties from verified teams, and posting recruiting bounties for verified recruiters.
What is the best way to find Web3 jobs?
Maiev’s jobs feed collects open engineering, security, AI, product, design, QA, marketing, business development, trading and operations roles from the public job boards of Web3 teams, refreshed regularly. Filter by area, location, remote, salary and your own skills, then apply on the company’s own site: https://app.maiev.xyz/jobs.
How do I get hired in Web3 without a CV?
Sign in to Maiev with GitHub and your public code is ranked by skill within seconds. Add your work history and ask colleagues who worked with you to validate it. Companies search the leaderboards and send roles directly to the contributors they want.
How are product, design and QA people ranked?
Product, design and QA skills have no code to read, so they start from work history: 40 + 330 × √(experienced years), where each role counts by how relevant it is to the skill, whether it has been validated, and how recent it is. People rank as soon as they add the skill; hearts and validations move them up.
Is there a leaderboard of Web3 developers?
Yes. Maiev has public leaderboards for each skill at https://app.maiev.xyz/leaderboards: Solidity, Rust, Move and 40 more languages, smart contract security, AI, product, design and QA, plus ecosystem boards such as Ethereum and Solana. The scoring formula is public.
Can recruiters and agencies use Maiev?
Yes. In-house teams, recruitment agencies and independent recruiters can all hire on Maiev. Agencies verify their own domain; independent recruiters without a company domain are verified with their first credit top-up. Recruiters can name the client on each role or keep it confidential, and can bid on roles posted on the bounty board.
Can AI assistants and agents use Maiev?
Yes. Maiev has a public, read-only MCP server at https://app.maiev.xyz/mcp that any AI assistant or agent can connect to, to search Web3 jobs, read a listing, see a skill’s leaderboard, look up salaries and learn how hiring on Maiev works. Setup and the JSON API are at https://app.maiev.xyz/agents.
When does Maiev launch?
Maiev is in early access at app.maiev.xyz. The jobs feed, salary index, sign-in with GitHub, Google or X, skill leaderboards, verification, the bounty board and hiring accounts for companies, agencies and independent recruiters (search, roles, hunts and chat) are open now. Updates are posted on X at @maievxyz.
12Disclaimer
This is a draft. Everything in it, including features and pricing, may change before launch. It describes a product in development and is not financial, legal or tax advice. Official announcements are published only on maiev.xyz and on X at @maievxyz.