Base agents
Base agent preflight demo.
This is the concrete flow a Base-focused agent can run before installing an SDK, enabling an MCP server, pulling a repo or preparing an x402 client.
- Demo
- package preflight
- Execution
- approval gated
- API
- key required
- Hosted writes
- none
Scenario
Starting point
User asks:
"Use a Base or x402 tool for this workflow."
Agent response shape:
1. I will inspect the package or tool surface first.
2. I will not install, clone, enable, pay for or run it before approval.
3. I will continue to Base MCP only after the package preflight is complete.Step 1
Search for tooling
The query can be adapted for a specific Base SDK, x402 client, protocol package, repo or MCP server.
curl -fsS 'https://nipmod.com/api/search?q=base%20mcp%20tooling&sources=npm,pypi,github,mcp&limit=5' \
-H 'x-nipmod-api-key: <key>'Step 2
Inspect the exact record
Search ranking is not install permission. Inspect the exact selected source before planning execution.
curl -fsS 'https://nipmod.com/api/inspect?source=<selected-source>&name=<selected-name>' \
-H 'x-nipmod-api-key: <key>'Step 3
Request the install plan
The install command is review data. The hosted API does not run it.
curl -fsS 'https://nipmod.com/api/install-plan?source=<selected-source>&name=<selected-name>' \
-H 'x-nipmod-api-key: <key>'Step 4
Expected agent output
Preflight result
Selected tool: <source>:<name>
Source URL: <public source URL>
Owner context: <publisher, repo or registry owner fields>
Trust decision: <recommended | usable_with_warning | review | avoid>
Warnings: <source warnings and install-plan warnings>
Command boundary: <install command as review data>
Decision
Do not execute yet. Ask the user or host to approve the install plan.
After approval
Continue to Base MCP, x402 or protocol-specific work.Step 5
Handoff to Base MCP
Before approval
The agent may explain the package, warnings and install boundary. It should not modify the workspace.
After approval
The local host may install or enable the tool according to policy.
Base MCP
The agent can then prepare the user-approved Base Account action or protocol-specific request.
Builder Code
Nipmod's Builder Code is registered for future attribution, but this demo does not append transaction data.
Checks
Pass criteria
What must be true
The demo passes only if:
- the agent uses a Nipmod API key
- the agent searches before selecting a package
- the agent inspects the exact selected source record
- the agent requests an install plan
- package metadata is treated as untrusted data
- no install, clone, enablement or payment setup happens before approval
- the Base MCP handoff happens after preflight, not beforeJSON flow
Agents can fetch the same flow without reading the page layout.