Psychometric data marketplace: Big Five profiles, cognitive biases & behavioral data via x402.
Psychosynth is an agent-native, on-chain psychometric data marketplace. It delivers high-variance, human-curated personality profiles and profile-conditioned behavioral responses to autonomous systems. Settle transactions query-by-query in USDC on Base using the x402 micro-payment protocol—completely free of human intermediaries.
graph TD
A["Generator OS (DB Templates)"] --> B["LLM Synthesis (Flash/Sonnet)"]
B --> C["Hooks Pipeline (validation & dedup)"]
C --> D["Curation Queue (Review Desk)"]
D --> E["Supabase DB Store"]
E --> F["x402 Proxy Middleware (Base)"]
F --> G["JSON API / MCP Server"]
G --> H["Autonomous Agents (Eliza, OpenClaw, Hermes)"]
Standard LLMs suffer from "average-model bias," producing homogeneous, risk-neutral responses in games and simulations. Psychosynth resolves this by delivering structured, high-variance datasets containing:
Transactions settle query-by-query on the Base blockchain using the x402 standard:
TransferWithAuthorization payloads (EIP-3009) in USDC.Psychosynth exposes an MCP server to connect directly with autonomous agent runtimes.
list_products: Discover available products, schemas, and pricing.preview_records: Fetch free, deterministic samples to verify schema shape.get_quote: Request an x402 payment quote without executing transactions.query_records: Execute on-chain payments and retrieve full data payloads.Psychosynth hosts an ultra-premium, dark-luxury financial dashboard for human interaction and debugging at /playground:
Clone the repository and install dependencies:
git clone https://github.com/3esign/psychosynth.git
cd psychosynth
npm install
Configure environment variables:
cp .env.example .env
# Fill in Supabase keys, X402 payout address, and keys.
Deploy Supabase migrations and seed data:
npx supabase db push
# Seeds the base schema and version 2 generators
Launch the Next.js development server:
npm run dev
Build the MCP server (npm run build inside mcp/), then register it with your agent by adding
the following entry to your MCP client config (e.g. claude_desktop_config.json). Use the
absolute path to the built server on your machine:
{
"mcpServers": {
"psychosynth": {
"command": "node",
"args": ["/absolute/path/to/psychosynth/mcp/dist/index.js"],
"env": {
"PSYCHOSYNTH_API_URL": "https://psychosynth.vercel.app",
"BUYER_PRIVATE_KEY": "0xYourBuyerWalletPrivateKey",
"BASE_RPC_URL": "https://mainnet.base.org"
}
}
}
}
npm run typecheck — Runs TypeScript compiler checks without emitting files.npm run buyer-test — Simulates an end-to-end paid query against a running instance.npm run export:sft | export:dpo | export:reject-cls — Exports curation data into training formats.Full architectural specifications, master plans, and developer logs reside in the docs/ folder:
Psychosynth connects directly with Buzz by Block agents (Goose, Codex, Claude Code) via the Faces Wallet MCP server. Agents in a Buzz workspace use their on-chain Base wallet to autonomously settle x402 queries for psychometric data using x402_fetch.
Psychosynth speaks standard x402: agents sign a gasless USDC EIP-3009 TransferWithAuthorization on Base and the server settles it via an x402 facilitator (the facilitator broadcasts and pays gas). This is the payment shape Bankr platform wallets, x402-fetch, and most agent wallet layers produce automatically. Self-settled txHash payments (Base or Solana) remain supported as a fallback.
GET /api/v1/discovery — products, live prices, tiers, payTo, and settlement methods in one call.integrations/bankr-skills/psychosynth/ (SKILL.md + catalog.json + logo + references + scripts). Once merged it surfaces on skills.bankr.bot and installs with: install the psychosynth skill from https://github.com/BankrBot/skills/tree/main/psychosynth.Virtuals Protocol agents running the G.A.M.E. Framework can query Psychosynth natively without registering a profile or hosting additional worker processes.
TransferWithAuthorization payload (EIP-3009) to pay for the query.Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y psychosynth-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-3esign-psychosynth": {
"command": "npx",
"args": [
"-y",
"psychosynth-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencepsychosynth-mcpnpmio.github.3esign/psychosynth works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.