# M2M Sentinel — LLM Interface & Discovery Index > Before signing on Base: what can this contract do? Pause, freeze, mint, self-destruct, or delegate execution elsewhere -- read from deployed bytecode, with proxies resolved and the trust level stated. Evidence for your policy, never a safety verdict. M2M Sentinel serves machine consumers on Base (eip155:8453; chainId 8453). Contract observations are factual static evidence with `notASafetyGuarantee: true`; they are not safety or exploitability claims. ## Authoritative machine surfaces - Full context: https://m2msentinel.com/llms-full.txt - OpenAPI 3.1.0: https://m2msentinel.com/openapi.json - Agent manifest: https://m2msentinel.com/agents.txt - Agent skill: https://m2msentinel.com/SKILL.md - Official MCP server metadata: https://m2msentinel.com/.well-known/mcp/server.json - Compatibility MCP manifest: https://m2msentinel.com/mcp.json - x402 v2 catalog: https://m2msentinel.com/.well-known/x402 - Measured Base exposure sample: https://m2msentinel.com/research.html ## Integration - MCP Streamable HTTP: https://api.m2msentinel.com/mcp - MCP stdio: `npx -y @m2msentinel/sdk mcp` - Legacy HTTP+SSE compatibility: https://api.m2msentinel.com/sse and https://api.m2msentinel.com/messages - npm: `npm install @m2msentinel/sdk@1.2.7` - Python: `pip install m2m-sentinel==1.2.7` ## API-key/RapidAPI metered REST capability - `POST /v1/transaction/preflight` — Resolve the executing target for one Base transaction - access: API key or verified RapidAPI proxy authentication; one existing decision credit after a valid evidence response is prepared. - x402: not-payable; no x402 price - description: API-key/RapidAPI metered transaction-specific evidence. Accepts one strictly validated Base mainnet transaction, pins one observation block before state-bearing reads, identifies the supplied four-byte selector and resolved implementation or Diamond facet, returns bytecode hashes, capability evidence and an eth_call observation when possible. Incomplete or unsupported paths stay explicit. The caller owns policy before signing. This route is not x402-payable and has no x402 price; an unauthenticated request receives the normal protected-route 401 response. The transaction preflight route is not x402-payable and has no x402 price; use an API key or verified RapidAPI proxy authentication. ## Paid implementation sprints - Growth Integration Sprint: $299 (the existing Growth plan price); one codebase, one Base signing boundary, one runnable proxy/EIP-7702-aware preflight patch, and a bounded seven-day handoff. - Pro Production Sprint: $999 (the existing Pro plan price); up to two transaction flows, runnable integration patches, and deployment/handoff documentation. - Purchase and scope: https://m2msentinel.com/integration-sprint.html. RapidAPI card access is at https://rapidapi.com/ApplicationsForTheFuture/api/m2m-sentinel-api; ULTRA maps to Growth and MEGA maps to Pro. - Intake is a non-secret email handoff. Never send private keys, seed phrases, raw API keys, wallet credentials, or unreviewed private-repository access. No safety verdict, exploit detection, guaranteed deployment, uptime, priority support, or ongoing SLA is promised. ## Runnable technical proofs - Openfort-compatible EIP-7702/ERC-4337 boundary: https://m2msentinel.com/proof-openfort.html (source: `https://github.com/M2M-Sentinel/m2m-sentinel-sdk/blob/main/examples/proofs/openfort-7702-preflight.ts`). It observes before an Openfort-style `signUserOperation` callback and keeps unresolved delegation explicit; it is not an official Openfort integration or partnership. Official references: https://github.com/openfort-xyz/openfort-7702-account, https://7702.openfort.io/. - Locus-compatible standalone dynamic payment boundary: https://m2msentinel.com/proof-locus.html (source: `https://github.com/M2M-Sentinel/m2m-sentinel-sdk/blob/main/examples/proofs/locus-compatible-agent-payment.ts`). It observes the selected Base target before a mock payment callback; it makes no Locus partnership claim. Public references: https://docs.paywithlocus.com/, https://paywithlocus.com/developers. - Both proofs are runnable with Node.js 22+, use hermetic mocks, never request credentials or executable private keys, and fail closed when caller policy sees unresolved evidence.