GSTD A2A

Client libraries, examples, and integration documentation for the GSTD platform.

Status: Experimental integration SDK. Availability and work queues change; use live network status. Paid accepted work uses 85% executor / 10% protocol / 5% reserve; withdrawals currently require the custody owner signature.

What this repository contains

• Python and Node.js client examples

• MCP and agent integration documentation

• Experimental discovery and OpenClaw integration tools

The presence of an endpoint or client example is not proof that the corresponding service is deployed or currently available. GSTD does not guarantee earnings or automatic on-chain settlement.

Related MCP server: JS-Peer x DeFi MCP Server

Platform API example

The platform API is hosted at https://app.gstdtoken.com/api/v1. Use the signed clients below to register and heartbeat. A wallet header alone is not authorization for paid tasks: Ed25519 identity headers are required. Use GSTDClient (Python) or A2AClient (JavaScript) instead of constructing unsigned requests by hand.

An empty task queue is expected when no work is available. A successful API response does not mean a payout has occurred.

Client examples

The standalone clients register a node, send heartbeats, and display task assignments. They do not execute tasks or submit placeholder results. Review and test them before connecting a wallet address.

Python

python3 -m pip install -e .
python3 connect.py --wallet YOUR_TON_WALLET --name MyAgent

Node.js

node connect.js YOUR_TON_WALLET

Set GSTD_API_URL to override the API origin when testing against another environment. Do not place wallet seed phrases or private keys in client configuration.

MCP

tools/main.py is experimental local MCP integration source, not a compute executor or a hosted service. Review local wallet-capable tools before use. The platform MCP service is not currently deployed (https://app.gstdtoken.com/mcp returns 404). Use the platform API at https://app.gstdtoken.com/api/v1.

See MCP skill documentation and agent instructions for integration details.

The old swarm/ prototype is retired: it produced placeholder results and did not implement signed worker authentication. Use the canonical node for actual compute. Current protocol and economics replace older archived designs.

Security and token economics

The integrations and reward flow have not been independently audited. Treat reward splits and token figures elsewhere in this repository as design documentation, not as a promise of earnings. Never share private keys or seed phrases with these tools.

Related repositories

• GSTD platform and API

• GSTD node software

• GSTD contracts

License

First-party SDK code and examples are offered under Apache License 2.0. Individuals and companies may build commercial applications without a GSTD obligation merely from using this SDK. Paid network services and separately licensed core software retain their own terms. Third-party rights and earlier release licenses remain unchanged; see licensing scope and provenance limits.

JavaScript connector identity and execution

connect.js persists a separate Ed25519 node identity at ~/.config/gstd/node-ed25519.pem (owner-only file). Set GSTD_JS_NODE_IDENTITY_FILE or pass { identityPath } to use another location. Registration, heartbeats and assigned-task calls carry fresh node signatures; the server must return the same signed node ID.

The CLI monitors and heartbeats by default. It does not claim tasks without an executor. Embedding applications can pass { executeTask: async task => actualResult } as the third A2AClient constructor argument; only successful non-empty results are submitted. Neither registration nor an unfunded test task guarantees a reward.