Skip to main content

CreatorBid

CreatorBid — a reference card for a crypto project: what the product does and how verifiable the project’s key claims are; also — alignment with the Decentralized AI thesis (DecAI Fit).

CreatorBid — an AI/Agents and Launchpad ecosystem: launching, growing and monetizing AI agents with an onchain economy (Agent Keys) and the native token BID (BNB Chain / multi-chain).

Disclaimer

Important: this page is a reference overview of the project. Within DecAIHub, we separately record a verification based on open sources within the AI thesis (what is real AI/onchain/why a token, and which sources this is based on).
This is not financial advice and not a recommendation to buy/sell/hold any asset. We do not assess price, returns, or entry/exit timing.
Conclusions are based on publicly available materials found as of the verification date. The absence of confirmation does not imply the absence of the technology.

TL;DR (for readers who are not into AI)

  • What it is: a platform where creators launch “agents” and their onchain tokens (Agent Keys), and users can participate in the agents’ economy (purchase/staking/endorsements).
  • Who it’s for: creators of AI agents, users/communities who want to support agents and get access/perks.
  • Why onchain/token: onchain records ownership of Agent Keys, taxes/treasuries and the distribution of emissions; the BID token is the “fuel” for payments/endorsements/incentives (per the docs).
  • What you can actually touch (Tier‑1): the CreatorBid web product (see links_* → App / Demo) and the step‑by‑step “How to use” guides in the docs.

How it works (very briefly)

  1. The user does: creates/launches an AI agent or buys the Agent Keys of a specific agent.
  2. The system does: launches Agent Keys (ERC‑20) via a bonding curve and moves liquidity to a DEX once the conditions are met; a “Safe smart contract wallet” is created for each agent (per the docs).
  3. The user gets: access/perks from the agent, the ability to stake Agent Keys and to participate in BID emissions/endorsement mechanics.
  4. Where the blockchain is: Agent Keys are onchain tokens; there are onchain taxes/treasuries and onchain lock/cooldown mechanics.
  5. Token role (if any): BID is used for service payments/endorsements and in emission mechanisms (buyback‑based emissions and BID vault levels).

Quick links: AI thesis fit

Project passport

Field Value
Project name CreatorBid
Also known as (aliases) Creator Bid; $BID
Logo (logo) ../assets/169_creatorbid_logo.png
Token symbol (ticker) BID
Category AI/Agents | Launchpad | Social
Primary chain (chain) BNB Smart Chain
Type EVM
Network status mainnet
Consensus (consensus) PoSA (BNB Smart Chain; 21 validators)
Launch date (launch_date) —
Project status (status) active
Token (standard) BEP-20
Token contract 0xa1832f7F4e534aE557f9B5AB76dE54B1873e498B
Token model (token_type) utility (payments + endorsements + incentives)
Max supply 1,000,000,000 BID (cap in the token code)
Issuance capped; part of the emissions is buyback‑linked (bi‑weekly) per the docs
Tokenomics (tokenomics, brief) emissions v0.2: once every 2 weeks, sourced from buyback (30% protocol fees → buyback; emissions = 3× buyback)
Governance — (not described as a DAO; the token admin is a multisig owner)
Admins/keys the token is Ownable; owner = multisig 0x47Bc406344A7721C534D77970d21574867228B92; there is a setMinter for the NTT bridge
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI agent creation + training (content/posting)
Use‑case (use_case) on-chain economy for AI agents + their communities
DecAI Fit — AI thesis fit 5/6 — high alignment with the Decentralized AI thesis
DecAI Fit component summary 2 / 2 / 2 / 3
Last verified 2026-02-11

General project overview

CreatorBid describes itself as an “Agent Ecosystem” that gives users tools to launch and monetize AI agents “on‑chain and across social platforms”. An important element is a token‑based economic model: each agent has its own “Agent Key” (ERC‑20), which is launched via a bonding curve and moves into DEX liquidity, while a share of the transactions funds the agent’s treasury and the protocol.

Note on networks (passport normalization): the passport lists BNB Smart Chain (per the BID token) as the primary chain. Mentions of Base/Agent Keys remain in the text as context.

The native token BID is used as the ecosystem’s utility token: payments for services, endorsements, incentives and emissions/rewards.

Features/modules

  • Agent Keys (ERC‑20) for AI agents: bonding curve → DEX migration; agent treasury (Safe wallet).
  • Staking Agent Keys: lock/cooldown (14 days) and “gated services” + BID emissions via DIM (per the docs).
  • BID Vault / BID Levels: levels (1–10) based on a time‑weighted BID lock and activity, affecting allocations/multipliers (per the docs).
  • BID emissions: bi‑weekly emissions tied to BID buybacks from protocol revenue (per the docs).
  • How‑to sections: creating/training an agent, content generation, auto‑posting/replies, Telegram integrations (per the docs).

Typical scenarios

  • Scenario 1 (creator): creates an AI agent → launches Agent Keys → receives a treasury and a monetization model.
  • Scenario 2 (participant): buys Agent Keys → locks/stakes them → gets access to the agent’s premium services and a share of incentives/emissions.
  • Scenario 3 (BID participant): locks BID → raises their BID Level → gets more weight in the distribution of emissions and access to curated launches.

Getting started (wallet/network)

  • What you need: an EVM wallet (for the onchain part) and access to the web product.
  • Network/chain: BNB Chain (BID); Agent Keys can be on Base and BNB (per the docs).
  • Fees: gas of the corresponding network + DEX fees; taxes/fees per the token models (Agent Keys sell tax, etc., per the docs).

Architecture/tech (non‑AI)

  • Components: the web application + AI backend (generation/training/posting) + onchain contracts of the BID and Agent Keys tokens, staking contracts and vault mechanics.
  • Participant roles: agent creators, participants/stakers, endorsers, the protocol.
  • Where logic runs: AI logic (content/training) — offchain; the economy (Agent Keys, vault/lock, emissions‑related rules) — onchain (EVM).
  • Dependencies: DEX (PancakeSwap/Uniswap — mentioned), Safe wallets, RPC.

Token/economics (expanded, no forecasts)

  • BID token utility: payments for services, endorsements and incentives (per the docs).
  • Protocol necessity drivers: BID participates in the level mechanics (BID vault) and in the emissions system; without it, the claimed incentives model does not work in its current form.
  • Who pays fees: ecosystem participants; the docs also describe a sell tax for Agent Keys (up to 3%).
  • Where fees go: Agent Keys sell tax: 2% to the Agent Treasury (Safe wallet), 1% — protocol revenue (per the docs); BID emissions are linked to buybacks from protocol revenue (per the docs).
  • Issuance/burn: the docs describe emissions v0.2 once every 2 weeks; “Sourced from protocol revenue”: 30% of protocol fees (in ETH/BNB) go to BID buybacks, emissions = 3× buyback (per the docs).
  • Security/incentive mechanisms: locking BID (vault) raises the BID Level and the share of emissions; staking Agent Keys gives access to gated services and emissions; unlocking Agent Keys — a 14‑day cooldown.
  • Distribution and token issuance schedule: the docs contain an allocation/vesting chart (image); exact numbers/percentages — see the primary source.
  • Treasury: each agent has a Safe wallet (per the docs) + protocol revenue.

Governance

  • Who makes decisions: the team/protocol operator; for the BID token — owner = multisig (see the passport and links_* → Explorer).
  • How protocol parameters change: via contract/product updates; a public DAO/Snapshot process is not described in the reviewed Tier‑1 sources.
  • Where decisions are discussed/made: Website/Docs/X/Telegram (see links_*).
  • Keys/multisig: the token owner (multisig) is known from the explorer; the keys/threshold governing the remaining protocol contracts were not found in the reviewed Tier‑1 sources.

Security and incidents

  • Audits: — (no public Tier‑1 audit reports were found in the reviewed sources).
  • Bug bounty: —.
  • Incidents: — (no public postmortems/incidents were found in the reviewed sources).
  • Threat model: smart contract risks of Agent Keys (bonding curve, tax/treasury), administration key risks (multisig/owner), as well as risks of the offchain AI layer (training/posting/integrations).

Project status and timeline

  • Current status: active (the product and the BID token on BNB Chain mainnet; see links_*).
  • Key releases/milestones: —.
  • Roadmap: — (in links_* the Roadmap field = —).

Ecosystem/integrations

  • Integrations: BNB Chain + (for Agent Keys) mentions of Base/BNB; a Safe smart contract wallet for the agent treasury; DEX liquidity (migration to a DEX).
  • Partners: — (not listed as a verifiable list in the reviewed Tier‑1 sources).
  • Where it’s actually used: launching/monetizing AI agents via Agent Keys and onchain incentives (see links_* → Docs/Website).

AI component of the project

  • What is real AI here? the Tier‑1 docs describe the functions of agent creation/training, content generation and auto‑posting/replies — this is the AI product layer.
  • What is truly onchain? Agent Keys (ERC‑20), vault/lock, staking contracts and emissions logic (per the docs), plus the BID token.
  • Why is a token needed? BID is used as “fuel” for payments/endorsements and incentives, as well as for building levels (BID vault) and distributing emissions (per the docs).
  • Red flags (based on the information found): AI‑washing — medium (no technical details of the models); onchain‑washing — low (the economy is tied to tokens/locks); double‑check the audit/addresses of the staking contracts if critical for risk.

DecAI Fit component summary

  • DecAI Fit: 5/6 — high alignment with the Decentralized AI thesis
Component Level Score
AI reality medium 2
Onchain necessity medium 2
Token necessity medium 2
Evidence Tier‑1 present 3
Details

AI reality

AI_0 — AI intent (Tier‑1 roadmap) (1/0)

  • AI_0 (decision): 0
  • Claim (one line): AI agents are described as a functional product (create/train/generate), so the intent flag is not used.
  • Evidence: Tier‑1 — https://docs.creator.bid/how-to-use-creatorbid
  • Why sufficient / why not (one line): the docs describe working user scenarios.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): users create/train AI agents and use them for content generation and auto‑posting/replies.
  • Evidence: Tier‑1 — https://docs.creator.bid/how-to-use-creatorbid
  • Why sufficient / why not (one line): this is a direct description of the product’s AI functionality.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): the “How to use” sections describe step by step how to work with an agent (creation, training, content generation, Telegram integration).
  • Evidence: Tier‑1 — https://docs.creator.bid/how-to-use-creatorbid
  • Why sufficient / why not (one line): the existence of user guides for working features serves as demo evidence.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://docs.creator.bid/how-to-use-creatorbid
  • Why sufficient / why not (one line): model quality metrics/benchmarks are not published.
  • Conflict note (if any): —

AI_4 — tech description/architecture/versions (1/0)

  • AI_4 (decision): 0
  • Claim (one line): there is no technical description of the models/inference/training architecture (there are user guides and an onchain economy).
  • Evidence: Tier‑1 — https://docs.creator.bid/how-to-use-creatorbid
  • Why sufficient / why not (one line): without technical details/versions — flag 0.
  • Conflict note (if any): —

Onchain necessity

OC_1 — contracts/addresses/chain (1/0)

  • OC_1 (decision): 1
  • Chain: BNB Chain (BSC)
  • Addresses/identifiers: BID token: 0xa1832f7F4e534aE557f9B5AB76dE54B1873e498B
  • Evidence: Tier‑1 — https://bscscan.com/token/0xa1832f7F4e534aE557f9B5AB76dE54B1873e498B
  • Why sufficient / why not (one line): the token address is confirmed by the explorer; the code shows a max total supply cap of 1B.
  • Conflict note (if any): —

OC_2 — onchain beyond just a token (1/0)

  • OC_2 (decision): 1
  • What useful logic is onchain: Agent Keys (ERC‑20), bonding curve → DEX migration, staking/lock/cooldown and Safe wallets for the agent treasury (per the docs).
  • Evidence: Tier‑1 — https://docs.creator.bid/overview/tokenomics/agent-keys-and-revenue-model
  • Why sufficient / why not (one line): the documentation describes onchain mechanisms on top of the base token.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: theoretically, the platform could be implemented as a Web2 service with offchain accounting, but the current model of economic composition (tokens/DEX/locks) is tied to the blockchain.
  • Evidence: Tier‑1 — https://docs.creator.bid/overview/tokenomics/agent-keys-and-revenue-model
  • Why sufficient / why not (one line): onchain provides verifiability/composability, but is not a physically inevitable condition for the AI functions.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, BID.
  • Evidence: Tier‑1 — https://docs.creator.bid/overview/tokenomics/usdbid-token ; https://bscscan.com/token/0xa1832f7F4e534aE557f9B5AB76dE54B1873e498B
  • Why sufficient / why not (one line): the token is confirmed by the docs and the explorer.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 1
  • Claim (one line): BID is claimed as the token for service payments in the ecosystem.
  • Evidence: Tier‑1 — https://docs.creator.bid/overview/tokenomics/usdbid-token
  • Why sufficient / why not (one line): the docs directly describe BID as a “native utility token… driving service payments”.
  • Conflict note (if any): —

TK_2 — incentives/collateral/penalties (1/0)

  • TK_2 (decision): 1
  • Claim (one line): BID emissions are distributed to BID Level holders / agent stakers / endorsers; locking BID raises the level and the share of emissions.
  • Evidence: Tier‑1 — https://docs.creator.bid/overview/tokenomics/bid-emissions ; https://docs.creator.bid/overview/tokenomics/what-is-a-bid-level
  • Why sufficient / why not (one line): the incentive mechanics of emission distribution and the lock conditions are described.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): governance via BID is not described as a separate mechanism in the Tier‑1 docs.
  • Evidence: Tier‑1 — https://docs.creator.bid/overview/tokenomics
  • Why sufficient / why not (one line): the emphasis is on utility and incentives.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): BID is built into the emissions mechanism (buyback‑linked emissions, vault levels), so by design it is not a “cosmetic” component.
  • Evidence: Tier‑1 — https://docs.creator.bid/overview/tokenomics/bid-emissions ; https://docs.creator.bid/overview/tokenomics/what-is-a-bid-level
  • Why sufficient / why not (one line): the incentives design is tied to the token and its locks.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.creator.bid/how-to-use-creatorbid The existence of an AI product (agent creation/training, content generation, integrations)
Tier‑1 https://docs.creator.bid/overview/tokenomics/agent-keys-and-revenue-model The onchain economy of Agent Keys: bonding curve, DEX migration, sell tax and Safe wallet, staking/cooldown
Tier‑1 https://docs.creator.bid/overview/tokenomics/usdbid-token The role of BID: service payments/endorsements/incentives
Tier‑1 https://docs.creator.bid/overview/tokenomics/bid-emissions Emissions mechanics (bi‑weekly, buyback‑linked, distribution by groups)
Tier‑1 https://bscscan.com/token/0xa1832f7F4e534aE557f9B5AB76dE54B1873e498B The BID token address and parameters/code (Ownable, cap 1B, multisig owner)

No comments to display

Back to top