Base agents

Nipmod for Base agents.

Base MCP gives agents a wallet and onchain action surface. Nipmod sits before package, SDK, CLI and MCP decisions so the agent can inspect what it is about to install or enable.

Position
preflight
Machine spec
public
Hosted writes
none
Builder Code
registered

Fit

Where Nipmod belongs

Base MCP
Wallet, onchain action and ecosystem skill surface for agents.
Nipmod
Package intelligence before an agent installs or enables SDKs, CLIs, MCP servers, models, repos or packages.
Boundary
Nipmod does not sign transactions, hold keys, create wallet approvals or replace Base MCP.
It returns source context, trust signals and install plans.

Flow

Package preflight for Base agents

1
The agent needs a Base ecosystem package, SDK, CLI, MCP server or repo.
2
The agent calls Nipmod search across npm, PyPI, GitHub and MCP sources.
3
The agent inspects the exact source record instead of trusting package text.
4
Nipmod returns trust signals, warnings and a safe install plan.
5
The user or host approves any local install or tool enablement.
6
Only after that should the agent continue to Base MCP, x402 or protocol-specific work.

Calls

HTTP preflight

curl -fsS 'https://nipmod.com/api/search?q=base%20agent%20sdk&sources=npm,pypi,github,mcp&limit=5' \
  -H 'x-nipmod-api-key: <key>'

curl -fsS 'https://nipmod.com/api/inspect?source=npm&name=<package-name>' \
  -H 'x-nipmod-api-key: <key>'

curl -fsS 'https://nipmod.com/api/install-plan?source=npm&name=<package-name>' \
  -H 'x-nipmod-api-key: <key>'

Machine

Agent-readable entrypoint

JSON

Base preflight spec

Agents can fetch compact machine-readable workflows for Base-related package and tool decisions.

GET https://nipmod.com/base-agent-preflight.json
GET https://nipmod.com/base-agent-integration.json
GET https://nipmod.com/base-agent-demo-flow.json

Use this JSON before Base-focused package, SDK, CLI, MCP, repo or x402 client decisions.

Open preflight JSON

Prompts

Prompt pack

The public prompt pack includes the Base preflight instruction and links back to this page.

Open agent prompts

Outline

Integration outline

A concrete handoff model for using Nipmod before Base MCP, x402 or protocol-specific work.

Open integration outline

Demo

Reproducible flow

A step-by-step package preflight demo that agents and host teams can test directly.

Open demo flow

MCP

Read-only MCP option

Remote

Nipmod MCP

The hosted Nipmod MCP endpoint exposes package intelligence only. It does not read local files and does not write the caller workspace.

POST https://nipmod.com/api/mcp
Header: x-nipmod-api-key: <key>

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"nipmod.resolve","arguments":{"query":"Base MCP tooling","sources":["npm","github","mcp"]}}}
Prompt

Agent instruction

Use this when a Base-focused agent is about to add external tooling.

Before installing or enabling a Base ecosystem SDK, CLI, MCP server or package, use Nipmod.
Search the source, inspect the exact record, show trust signals and request an install plan.
Do not write files, install dependencies or enable tools until the user approves the plan.

Plugins

How this fits Base custom plugins

Base custom plugin
Defines how an agent calls a protocol API, CLI or MCP server and maps prepared output into Base MCP actions.
Nipmod preflight
Runs before that dependency is trusted. It inspects the SDK, CLI, MCP server, repo or package the agent wants to enable.
Clean integration
A Base skill or plugin can instruct the assistant to call Nipmod first, then continue to Base MCP after local approval.
No wallet custody, no signing, no transaction construction.
Base custom plugin:
  prepares unsigned calldata or maps protocol output to send_calls

Nipmod preflight:
  checks package/tool/source trust before that plugin, SDK or MCP server is installed or enabled

Base surfaces

What this helps with

Base MCP

Skill and toolkit dependencies

Agents can inspect package and MCP tooling before enabling a new onchain workflow.

x402

Paid service clients

Agents can check SDKs and API clients before spending through pay-per-request services.

Ecosystem

Partner tooling

Projects with SDK, CLI, MCP or package surfaces can become easier for agents to discover and review.

Builder Codes

Attribution boundary

Nipmod has a Base Builder Code reserved for future onchain attribution. The current hosted API does not append it because Nipmod does not build or submit transactions.

Base Builder Code: bc_vu9r71xi
ERC-8021 data suffix:
0x62635f76753972373178690b0080218021802180218021802180218021

Operator checklist

Ready without overclaiming

Base app verification
Homepage verification meta is present. Claim verified only after the Base app flow confirms it.
Builder Codes
Base Builder Code is registered for future attribution. Current hosted API remains read-only and does not append transaction data.
Base MCP
Nipmod can be used beside Base MCP today as a read-only package preflight, using HTTPS or the hosted Nipmod MCP endpoint.
Integration outline
Demo flow
Public wording
Use 'Base agent preflight' or 'integration path'. Do not say 'official Base integration' until Base lists or approves it.

Links

Base references

Base agents
Base MCP quickstart
Custom plugins
Builder Codes

Claims

What this page does not claim

No official listing
This page does not claim Base has approved, listed or endorsed Nipmod.
No wallet custody
Nipmod never holds user keys, Base Account credentials or signing authority.
No remote execution
The hosted API and hosted MCP endpoint do not install packages, clone repos or change workspaces.
No automatic trust
A recommended package is still review data. The local host decides whether anything is installed.
Open API referenceOpen integration outlineRun demo flowUse Nipmod MCPRead machine spec