Base agents
Base MCP integration outline.
This outline shows where Nipmod can sit in a Base MCP workflow: before external packages, SDKs, CLIs, MCP servers or paid API clients become part of the agent environment.
- Status
- outline
- Mode
- read only
- Handoff
- Base MCP
- Claim
- not official
Roles
Where each layer sits
Base MCP
Prepares user-approved onchain actions through Base Account and ecosystem skill plugins.
Nipmod
Runs before package or tool adoption. It returns source context, trust signals, warnings and install plans.
Agent host
Decides whether local install, clone, tool enablement or payment can proceed.
User
Approves local workspace changes and any Base Account transaction request.
Flow
Integration sequence
1
The agent identifies a Base SDK, CLI, MCP server, repo, package or x402 API client it wants to use.
2
The agent calls Nipmod search and keeps package metadata as untrusted data.
3
The agent inspects the exact source record rather than relying on a broad search result.
4
The agent requests an install plan and shows warnings, trust fields and command boundaries.
5
The local host or user approves any install, clone, enablement or paid request setup.
6
Only then does the workflow continue to Base MCP, x402 or protocol-specific action preparation.
Contract
HTTP calls
POST https://nipmod.com/api/keys/beta
{"label":"base-agent-preflight"}
GET https://nipmod.com/api/search?q=<tooling-query>&sources=npm,pypi,github,huggingface-model,huggingface-dataset,mcp&limit=5
Header: x-nipmod-api-key: <key>
GET https://nipmod.com/api/inspect?source=<source>&name=<name>
Header: x-nipmod-api-key: <key>
GET https://nipmod.com/api/install-plan?source=<source>&name=<name>
Header: x-nipmod-api-key: <key>Host prompt
Instruction for agent hosts
Before a Base-focused workflow installs or enables external tooling, call Nipmod.
Search for the SDK, CLI, MCP server, repo, package or paid API client.
Inspect the exact source record.
Request an install plan.
Show trust signals, warnings and command boundaries.
Continue to Base MCP, x402 or protocol work only after user or host approval.Plugins
Base skill or plugin note
Copy into a skill or plugin spec
# Package preflight
Before using this Base skill or plugin, inspect any required SDK, CLI, MCP server, repo or package through Nipmod.
Use:
- /api/search to find candidates
- /api/inspect to verify the exact source record
- /api/install-plan to review command boundaries
Do not install, clone, enable, pay for or run external tooling until the user or host approves the install plan.What this does not do
Nipmod does not create wallet approvals, sign requests, hold keys, append transaction data or replace Base MCP.
It only prepares package intelligence before external tooling enters the workflow.
Machine
Agent-readable outline
Integration spec
Use this when an agent host wants a stable outline instead of page text.
GET https://nipmod.com/base-agent-integration.json
GET https://nipmod.com/base-agent-demo-flow.jsonReproducible flow
The demo flow shows the exact sequence from package need to Base MCP handoff.
Acceptance
What a first integration should prove
Package decision
The agent can explain why it selected or rejected a tool.
Trust boundary
The answer includes source ownership, warnings and install-plan risk.
No blind execution
No package command runs before user or host approval.
Clean handoff
Base MCP work starts only after package preflight is complete.
No false attribution
Builder Code remains reserved until a real onchain or x402 transaction layer exists.