The smallest possible integration: a URL, a few query params, and an attributed member record. Designed to make the partnership-of-partners claim real in one afternoon, with room to grow.
EVERYONE.team is the cultural front door. When a member arrives through a partner platform, that partner can attach two pieces of attribution to the link, and the EVERYONE record will remember both. The partner can later read back the EVERYONE number for any of their members.
This is the minimum integration that makes the partnership real. It can stay this small or it can grow into deeper synchronization, webhook callbacks, or a full identity bridge. The choice is the partner's.
Send your member to:
https://everyone.team/in?partner=<partner_id>&pid=<your_member_id>partner. A short identifier for your platform. Assigned by EVERYONE per partnership. Lowercase, alphanumeric, up to 32 characters.pid. Your own member identifier for this person. EVERYONE stores it verbatim and uses it later to match back. Up to 128 characters. Opaque to EVERYONE; it never leaves your system in human-readable form.The member arrives at /in, sees the standard welcome, clicks Count me in, and is minted as a regular EVERYONE member. The attribution is recorded silently on the server side. No additional click or consent is required from the member; the attribution is between the two platforms.
The member receives the standard Level-0 EVERYONE artifact: a permanent number, an EVERY1 mark, a share link, and a counter. Their /me page works the same as any other member's. The partner attribution is stored on the member record as two fields: partner_source and partner_member_id.
Combined with a referrer (?from=<share_code>), partner attribution composes naturally. A member can be both attributed to your platform and brought in through another member's share link; both relationships are kept.
For partners that want to know the EVERYONE number assigned to one of their members, a lightweight read endpoint is exposed:
GET https://everyone.team/.netlify/functions/joinTeam?partnerSource=<partner_id>&partnerMemberId=<your_member_id>Returns the public member record (number, formatted number, share code, the member's chosen public profile fields if any). Authentication for this endpoint is per-partner and is set up at integration time; partners receive a signing key alongside their partner_id.
Nothing. EVERYONE.team is not a paid-traffic system; partners route members because the cultural project is the place where their members come pre-oriented to the values of the partner's offering, and because the bidirectional benefits (shared trust, attributed activity, recognition that flows back to whoever brought the buyer in) compose with the partner's own economics, not against them.
If the partner sells anything routed through EVERYONE.team in the future, the standard universal-participation principle applies: a meaningful share of any attributed sale returns to whoever brought the buyer in. Specific terms are set per partnership.
The integration itself is essentially free for us to support: it is a single URL, two query params, and four lines of code that already shipped. The cost EVERYONE.team takes on is the quality of the front-door experience itself. We commit to keeping /in clean, fast, mobile-first, free at Level 0, and to never selling, sharing, or exfiltrating partner-routed members' data.
The integration lets a member arrive through a partner platform, become part of the broader team-recognition system, retain their identity and relationships on the partner side, and (when the read-side ships) be reached back by the partner with the EVERYONE number attached. EVERYONE.team's mission-aligned cultural production becomes a recruitment channel for the partner in the most honest sense: members arrive pre-oriented, not pre-converted. The partner's depth (whatever the partner uniquely provides) becomes the operational layer EVERYONE.team does not need to rebuild.
This is the smallest possible step from "described" to "live." The next steps (read-back authentication, deeper synchronization, OAuth identity bridge, joint product surfaces) are all on the table and all optional. We start small. We build the next step when both sides want it.
Everything. EVERYONE.team does not become the system of record for the partner's members. The partner's members remain the partner's members. EVERYONE.team adds a layer (a number, a mark, a share link, a place in a broader team-recognition system) that is structurally additive, never extractive.
Email zak@everyone.team with: the partner name, a one-line description of the platform, and the desired partner_id string. We assign the identifier, you start sending members, the attribution is recorded from the first member through. No paperwork required for the write side; if read-back is wanted, we set up a signing key once and you are done.