Ecosystem · Developer API

Build on the
network’s API.

Every GenD capability is a REST namespace on the hub and on your app: identity and connect, projects and agents, gas and ledger, contracts and wallets, mail and content. Authenticated, versioned, signed where it matters.

Ten namespaces, bearer tokens, 401 by default.Issue 11 · API
The surfaceTen namespaces, bearer tokens, 401 by default.
Namespaces10on the hub and your apps
Routes350+registered across the plugin suite
AuthBearerinstall tokens, member OAuth, device tokens
Unauthenticated401nothing is served without credentials
SigningEd25519connect requests and plugin packages
PluginGenD Societythe open-source client that speaks this API
Namespaces

The API map

NamespacePluginWhat it covers
aipa/v1Davincii Ai (Leo)chat, files, templates, pages, BuddyPress, myCred points, WooCommerce analytics, OAuth exchange
em/v1Community Emailsinboxes, postings, chat forms, branded mail
psoo/v1Remote Projectsbusiness plan, sequences, ad sets, audiences, creatives, social accounts, devices
gs/v1GenD Societyweb shell, agents, invites, playlists, desktop releases, connect challenge
gend-chain/v1Contracts & Paymentsbalances, DGEN withdrawals, node stake and routing, scheduled contracts
gend-cp/v1Contracts & Paymentswallet, ledger, fund, EVM status, OAuth relay and pickup
gdc-app-manager/v1Vendor App Managerconnect protocol, migration, container domains, backups
gdc-gas/v1Vendor App Managertask catalog, usage, ledger, dispatch
gend-pm-sync/v1Remote Projectsdesktop ↔ hub project sync
gend-society/v1GenD SocietyOAuth login
Examples

Three calls to get oriented

connect a site
# signed with your install's Ed25519 key
POST https://gend.me/wp-json/gdc-app-manager/v1/connect/start
# ... owner approves at https://gend.me/connect/ ...
POST https://gend.me/wp-json/gdc-app-manager/v1/connect/complete
{ "install_token": "..." }

# then
GET /wp-json/gdc-app-manager/v1/install/{id}/health
Authorization: Bearer <install_token>
wallet & gas
GET /wp-json/gend-cp/v1/me
GET /wp-json/gend-cp/v1/wallet/balance
GET /wp-json/gend-chain/v1/balances/{user}/history

# network administrators
GET /wp-json/gdc-gas/v1/catalog
GET /wp-json/gdc-gas/v1/ledger
agents
POST /wp-json/gs/v1/agent/provision
POST /wp-json/gs/v1/agent/run
POST /wp-json/gs/v1/agent/send
POST /wp-json/aipa/v1/chat
POST /wp-json/aipa/v1/seq-task-chat
desktop releases
GET /wp-json/gs/v1/desktop/latest
GET /wp-json/gs/v1/desktop/info

# public update feeds
https://updates.gend.me/gend-society/gend-society.json
https://updates.gend.me/web-builder/latest.yml
Principles

How the API behaves

Signed connect

Sites prove identity with Ed25519 keys; owners approve in the browser; a five-minute single-use code buys the install token.

Identity protocol →

Per-member OAuth

Each WordPress user links their own gend.me wallet. Apps never hold a member’s password.

Device tokens

Nodes authenticate with device tokens on the device run-queue, never with a browser session.

Node operations →

Event-driven contracts

Payment, sales and reward events trigger Web App Contracts on the hub and on connected apps.

Smart contracts →

Open-source client

GenD Society is the plugin that speaks this API. Read it, fork it, or install it from the signed feed.

Society-Core →

Local first

Develop against a local workspace in the desktop client, then connect and migrate.

Desktop client →
Getting a token

Four steps to your first authenticated call

Register

Your gend.me identity is your API identity.

Create a group

Tokens are scoped to a group’s web app or connected site.

Connect or launch

Install GenD Society on a site and connect it, or launch a hosted app.

Call the API

Use the install token as a bearer; members use OAuth.

Ship something

The network is an API.

Register, connect a site and make your first call today.