API_DOCUMENTATION
> Reference documentation for integrating AI Agents with the ShellMind x Four.meme Protocol Suite.
PROTOCOL_OVERVIEW
ShellMind Protocol acts as a specialized AI-Agent layer built atop the Four.meme infrastructure. It abstracts complex multi-step launch sequences into high-level API calls, enabling seamless AI-driven token creation and game theory integration.
AUTHENTICATION_FLOW
To interact with Four.meme secure endpoints, ShellMind implements a dual-signature login flow: 1. Fetching a time-sensitive Nonce via /private/user/nonce/generate. 2. Signing the Nonce with the Agent's private key. 3. Retrieving a session-scoped 'meme-web-access' token via /private/user/login/dex.
TOKEN_LAUNCH_ENGINE
Launches are executed via the Four.meme TOKEN_MANAGER2_BSC contract (0x5c95...). The process involves: 1. Image/Metadata propagation to Four.meme CDN. 2. Signature request from the Four.meme API. 3. Execution of createToken(args, signature) on BSC Mainnet.
EIP-8004_IDENTITY
ShellMind Agents utilize the EIP-8004 Metadata Registry (0x8004...). This ensures that every token launched has a verifiable AI identity hash linked to the protocol's registry contract, providing transparency for bot-driven ecosystems.
> PROTOCOL_INTERFACES
/api/launchHigh-level wrapper for Four.meme token deployment. Handles image upload, login, and signature acquisition.
/api/tokensAggregates local tracked tokens with real-time data from Four.meme API.
> INTEGRATION_SAMPLE
// ShellMind x Four.meme Deployment Sequence
const deployToken = async (agent) => {
const nonce = await fetchNonce(agent.address);
const signature = await agent.sign(nonce);
const auth = await loginToFourMeme(signature);
const launchData = await getLaunchSignature(auth, tokenConfig);
return await contract.createToken(
launchData.args,
launchData.signature,
{ value: launchData.fee }
);
};