Skip to main content

Vector Space Biosciences

Vector Space Biosciences (VectorspaceAI) — 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).

Vector Space Biosciences (VectorspaceAI) — an AI/Data + Infra project on Ethereum (EVM), token (symbol: VXV).

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 service/documentation for building and visualizing datasets/relationships based on language modeling (embeddings) in a (biodata/biomed) context.
  • Who it’s for: research teams and developers who need datasets/tools for analyzing relationships and signals in scientific data.
  • Why onchain/token: the project has an ERC‑20 token, VXV; in public materials it is associated with “immutability / security / utility transactions”, but the criticality of onchain for the product is not proven.
  • What you can actually touch (Tier‑1): the “CMDB API / PPIN API” demo/guide on the website with examples and a link to a Jupyter Notebook.

How it works (very briefly)

  1. The user does: selects/calls an API (for example CMDB), sets the context/features and requests a matrix/dataset.
  2. The system does: applies language modeling/embeddings and data engineering pipelines to build a matrix of “context‑dependent” relationships and derived visualizations.
  3. The user gets: a dataset (matrix) and/or a visualization (for example heatmap/graph).
  4. Where the blockchain is: the VXV token exists on Ethereum; in the project materials the blockchain is mentioned as part of the approach to the immutability/security of datasets.
  5. Token role (if any): the documentation/descriptions claim support for “utility token transactions” (detailed rules of use/pricing were not found per Tier‑1 sources as of the verification date).

Quick links: AI thesis fit

Project passport

Field Value
Project name Vector Space Biosciences
Also known as (aliases) VectorspaceAI; VXV; VectorSpaceBio
Logo (logo) —
Token symbol (ticker) VXV
Category AI/Data | Infra
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) —
Project status (status) active
Token (standard) ERC-20
Token contract 0x7d29a64504629172a429e64183d6673b9dacbfce
Token model (token_type) —
Max supply 50,000,000 VXV
Issuance fixed
Tokenomics (tokenomics, brief) max supply: 50,000,000; ERC‑20
Governance company
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) language modeling + bioscience dataset pipelines
Use‑case (use_case) contextual relationship analysis in biodata
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary 3 / 1 / 0 / 2
Last verified 2026-02-11

General project overview

Vector Space Biosciences describes itself as a project/company that builds datasets and analysis tools based on language modeling (embeddings) and data engineering pipelines to find “hidden” and “context‑dependent” relationships in scientific data (including biomedical/biological data).
Pages describing the approach and documentation/demo for the API (CMDB/PPIN) are publicly available.

Features/modules

  • CMDB API: building a correlation matrix dataset based on language modeling.
  • PPIN API: building a graph network of interactions from the matrix.
  • Visualizations: heatmap/graph examples as output on top of the datasets.

Typical scenarios

  • Scenario 1: a researcher sets a context and receives a relationship matrix (dataset) for further analysis.
  • Scenario 2: a developer uses the demo/notebook to reproduce an example of building a heatmap/graph.

Getting started (wallet/network)

  • What you need: access to the documentation/demo (in a browser); for reproduction — Python/Jupyter (if using the notebook from GitHub).
  • Network/chain: Ethereum (for the VXV token).
  • Fees: onchain fees depend on operations with the token; the rules for paying for the API were not found per Tier‑1 sources as of the verification date.

Architecture/tech (non‑AI)

  • Components: website/documentation; API; demo materials; the VXV token on Ethereum.
  • Participant roles: API/dataset users; the team/service operators.
  • Where logic runs: dataset building and computations — offchain; the token — onchain (Ethereum).
  • Dependencies: sources of scientific data/publications (PubMed is mentioned) and the service infrastructure.

Token/economics (expanded, no forecasts)

  • Token utility: the project materials mention “utility token transactions” and the link between the blockchain and security/immutability for datasets.
  • Protocol necessity drivers: no explicit “does not work without the token” rules were found; the criticality of the token for the product is not proven.
  • Issuance: max total supply 50,000,000 VXV (see the explorer).

Governance

  • Who makes decisions: company (per public materials).
  • How product parameters change: via releases/updates of the service (a detailed governance process is not described).

Security and incidents

  • Audits: no confirmed public audits were found per Tier‑1 sources as of the verification date.
  • Bug bounty: not found per Tier‑1 sources as of the verification date.
  • Incidents: no public postmortems were found per Tier‑1 sources as of the verification date.
  • Threat model: typical risks — centralized API/data infrastructure and incomplete transparency of the “onchain/security” mechanisms.

Project status and timeline

  • Current status: the website and documentation are available; the VXV token on Ethereum (mainnet).
  • Roadmap: a separate roadmap page was not found per Tier‑1 sources as of the verification date.

Ecosystem/integrations

  • Integrations: examples/demos for the API and notebooks (Python/Jupyter) for reproduction.
  • Partners: the website lists “Partners & Collaborators” (as claims on the website; the details of the integrations were not verified).
  • Where it’s actually used: reproducible examples — on the CMDB/PPIN page (demo + notebook).

AI component of the project

  • What is real AI here? language modeling/embeddings and pipelines that build datasets/matrices of “context‑dependent” relationships; there is a demo and an API description.
  • What is truly onchain? the VXV token on Ethereum; in public descriptions the blockchain is associated with “immutability/security” for datasets, but specific onchain logic (other than the token) is not described.
  • Why is a token needed? claimed as a utility token for transactions/the approach to security/provenance; the specific mechanics making the token mandatory for access/use are not confirmed.
  • Red flags (based on the information found): onchain‑washing (no explicit onchain logic other than the token); token‑washing (it is unclear whether the token is mandatory for the service); what to double‑check — pricing/conditions of API access and the role of VXV in payment/access.

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): no separate roadmap/plan about AI as an “intent” was found (there is a description of the current technology).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): AI is described as an existing component, but without a roadmap/intention artifact we set 0.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): language modeling/embeddings are used to build datasets/relationship matrices and to identify “hidden relationships”.
  • Evidence: Tier‑1 — https://vectorspace.ai/ ; https://vectorspacebio.science/cmdb
  • Why sufficient / why not (one line): the official website/documentation explicitly describes the role of AI/ML and what exactly is built as the result.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): there is a demo/instructions for the CMDB/PPIN API and a link to a Jupyter Notebook on GitHub.
  • Evidence: Tier‑1 — https://vectorspacebio.science/cmdb
  • Why sufficient / why not (one line): the Tier‑1 page contains a “Get started”/demo and points to a reproducible notebook.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): no public metrics/benchmarks of the quality of the model/outputs were found per Tier‑1 sources as of the verification date.
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): there is a tech description of the approach (language models/embeddings, CMDB/PPIN API) and a whitepaper.
  • Evidence: Tier‑1 — https://vectorspacebio.science/cmdb ; https://vectorspace.ai/assets/Vectorspace_Whitepaper.pdf
  • Why sufficient / why not (one line): documentation/a whitepaper describing the components and the approach is present.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: VXV (ERC‑20): 0x7d29a64504629172a429e64183d6673b9dacbfce
  • Evidence: Tier‑1 — https://etherscan.io/token/0x7d29a64504629172a429e64183d6673b9dacbfce
  • Why sufficient / why not (one line): the token address and the network are confirmed by the explorer.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: no description of applied onchain logic (other than the token) was found per Tier‑1 sources as of the verification date.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): without explicit contracts/access rules/onchain accounting we set 0.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: it is not shown that without the blockchain the key functionality of dataset building/the API breaks down.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): without specific “onchain is critical” proof we set 0.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the VXV token exists (ERC‑20).
  • Evidence: Tier‑1 — https://etherscan.io/token/0x7d29a64504629172a429e64183d6673b9dacbfce
  • Why sufficient / why not (one line): the token is confirmed by 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): support for “utility token transactions” in the API architecture is claimed.
  • Evidence: Tier‑1 — https://vectorspacebio.science/cmdb
  • Why sufficient / why not (one line): this is a direct statement on a Tier‑1 page (without specific pricing/rules).
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): incentives/collateral/penalties with the token are not described.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): without an explicit incentives mechanism we set 0.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): governance via the token is not described.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): without a description of voting/a DAO we set 0.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 1
  • Claim (one line): per the sources found, it is not shown that VXV is irreplaceable (payments for the service can also be implemented without a separate token).
  • Evidence: Tier‑1 — https://vectorspacebio.science/cmdb
  • Why sufficient / why not (one line): the absence of proof of “only VXV” → we consider it replaceable and set 1.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://vectorspacebio.science/cmdb Description of the CMDB/PPIN API, “Get started”/demo and the claimed support for utility token transactions
Tier‑1 https://vectorspace.ai/assets/Vectorspace_Whitepaper.pdf The project’s whitepaper (tech description/context)
Tier‑1 https://etherscan.io/token/0x7d29a64504629172a429e64183d6673b9dacbfce The VXV token contract, parameters and links to official resources
Tier‑2 https://www.coingecko.com/en/coins/vectorspace/ Token profile (for reference: markets/ticker)
Tier‑3 https://spacebiosciences.medium.com/ Blog/posts (context/marketing; not primary technical evidence)

No comments to display

Back to top