These seven features are not open in the production portals. Current state gives the reason for each one. Apart from X account binding, each also has to pass further testing before it opens. Each limit applies to every account: no role, verification step, or payment lifts it. A missing permission, an unmet verification requirement, or an empty list has its own cause; start from Common questions for those.
| Feature | What it is | Current state | What to do now |
|---|---|---|---|
| Contributor Teams | A way for Contributors to work as a group: create a team, invite members, and manage its roster. Tasks, credentials, and earnings stay individual records. | Not open in production while it is tested. The production Contributor portal shows no Teams entry, so you cannot create a team, invite members, or manage a roster there. Team relationships already on record still appear under Roles & teams on the Passport page. | Take part individually: claim and submit a task. Contributor teams explains what a team relationship changes. |
| Playground | A trial space for a dataset: a fixed sample of real records, with aggregate questions and matching, so you can judge the data before paying for access. | Locked because its sample, aggregate and match-rate checks are still being finished; it opens for every beta organization when that work ships. The Playground entry under Data in the Developer portal is greyed, and a dataset's Open Sandbox button opens a Limited preview notice instead of the tool. | Judge a dataset from its Marketplace listing, and read data your organization is authorized for through the API. See Access and use data. |
| Marketplace snapshot license and ownership | Snapshot & license exports a versioned copy of a dataset under a signed license. Ownership & royalty records an offer to acquire ownership of it. | Not offered at any trust tier, because the services behind them do not exist yet: the Marketplace has no entry point for either, so no copy can be exported, no license signed, and no ownership offer recorded. Metered access, Subscription, and existing subscriptions are not affected. | Email hello@humanbased.ai with the dataset and intended use. Data access and usage rights lists what to confirm first. |
| Agent listing | Publishing your organization's own agent in Agent Exchange, so that other organizations can use it in their Campaigns and its calls earn your organization revenue. | Locked until payouts to listing organizations are settled, including for verified organizations. List an agent on the Your Agents page is disabled. Agents your organization already has listed keep running, and their calls and revenue stay on that page. | To use an agent in a Campaign, choose Wire in on a Humanbased-operated agent in Agent Exchange, then select it in an Agent Task. See Configure a workflow. |
| Contributor royalty detail | Your individual royalty records: amounts tied to later use of a dataset you contributed to, kept separate from task rewards. | Locked, because there is no royalty ledger to read from yet. In Earnings, choosing Royalties under Filter activity shows Royalties aren’t tracked yet. That view holds no individual royalty records and does not report a zero amount. | Use the Rewards filter for task rewards and Withdrawals for payments. See Understand your earnings. |
| Contributor Ownership | Your ownership records for accepted contributions: your share in the datasets they went into, and the royalties those shares earn. | Locked, because the share and royalty figures behind these records are not yet reconciled across the portal. The Ownership row in the Contributor sidebar is greyed with a lock, and opening it shows Ownership is not open yet. It unlocks when royalty accrual ships. | Nothing to do: the records exist for your accepted contributions and the page opens when royalty accrual ships. Use Earnings for task rewards and payments. |
| X account binding | Linking your X account to your Contributor account, under Social Account on the Account page. | Locked while the connection to X is being reconfigured. The X card shows a locked Connect, and it reopens on its own once the new configuration is in place. An X account linked earlier still appears there and can be disconnected. No Telegram card is offered. | Nothing on your side reopens it, so there is no need to retry. Email and wallet binding on the same page are separate and are not locked; see Account and sign-in. |
API Keys are not limited here: any member of an organizationThe Developer-side unit that holds Campaigns, data access, and funds can create one. The key form does show four permissions locked (Publish a version, submission, billing and signals), because no API operation checks them yet; each unlocks when one does. See Create and use an API Key.