FOXIFY / AGENT ACTIONS. Hosted preflight evaluates submitted intent; public source preview observes bounded code. The executor and provider own real effects.
PUBLIC MACHINE API

Machine Start

Connect to the hosted preflight. Test the limits first.

Free discovery needs no FOXIFY account or wallet. Paid calls need a compatible x402 signer and your own spending policy. A preflight verdict is advisory; your executor must enforce it and verify the provider-side effect.

Remote MCP endpoint

Configuration formats differ by client. This generic example names the endpoint; use your client's current schema.

{
  "mcpServers": {
    "foxify": {
      "transport": "streamable-http",
      "url": "https://foxify.pro/mcp"
    }
  }
}

VS Code MCP configuration

Use this servers entry in your VS Code MCP configuration. It is client-specific and does not configure an x402 wallet.

{
  "servers": {
    "foxify": {
      "type": "http",
      "url": "https://foxify.pro/mcp"
    }
  }
}
  1. Connect the URL above. No FOXIFY account or API key is required for free capability discovery.
  2. Call foxify_preflight_info to read the current tools, prices, network and boundaries.
  3. Paid tools require an x402-compatible client with a signer controlled by you. Connecting plain MCP is not payment acceptance.
  4. Use a paid preflight only after checking the exact charge and authority in your own policy.

Live payment-intent preflight · $0.05 USDC

LIVE · 402 challenge verified now
Observed 2026-11-07T08:50:10.149Z

This observation verifies an unpaid quote only. It is not proof of a paid call or delivered result.

curl -i -X POST https://x402.foxify.pro/preflight \
  -H 'content-type: application/json' \
  --data '{}'

The empty request above is only an unpaid discovery probe. It does not sign or spend anything.

Exact action-authority preflight · $0.25 USDC

For consequential actions, send the actual subject, tool, operation, exact target, canonical parameters, authority lifetime, retry state and required postcondition to:

POST https://foxify.pro/action-preflight

A valid action payload is required before this route can reach its payment challenge. The following is sample data with unverified caller assertions; it is for schema and unpaid 402 testing, not an authorization grant.

{
  "action_id": "sample-action-001",
  "nonce": "sample-nonce-12345678",
  "expires_at": "2026-11-07T09:05:11.246Z",
  "subject": {
    "id": "sample-agent",
    "identity_verified": false
  },
  "action": {
    "tool": "sample.create_item",
    "operation": "create_item",
    "consequence": "external_submission",
    "target": {
      "kind": "workspace",
      "id": "sample-workspace"
    },
    "parameters": {
      "title": "Sample only"
    }
  },
  "authority": {
    "expires_at": "2026-11-07T09:20:11.246Z",
    "subject_id": "sample-agent",
    "attestation_verified": false,
    "allowed_tools": [
      "sample.create_item"
    ],
    "allowed_operations": [
      "create_item"
    ],
    "allowed_targets": [
      {
        "kind": "workspace",
        "id": "sample-workspace"
      }
    ],
    "max_attempts": 1,
    "allow_retry": false,
    "postcondition_required": true
  },
  "execution": {
    "attempt": 1,
    "prior_outcome": "NONE",
    "retry_authorized": false
  },
  "postcondition": {
    "type": "provider_readback",
    "authoritative_source": "sample.provider"
  }
}

FOXIFY evaluates the submitted claims. It does not independently authenticate your subject or execute, approve, or observe the downstream action. Bind real policy and verify the effect in the system that owns it.

Remote MCP

Production payment flow

  1. Send the intended request and read the 402 terms.
  2. Verify Base, native USDC, amount and recipient before signing.
  3. Sign with the caller's own wallet or x402 client. FOXIFY never needs the seed phrase or private key.
  4. Retry the same request once with the payment envelope.
  5. Persist the result and settlement evidence. If the outcome is ambiguous, reconcile it; do not create a second payment.

Public discovery

FOXIFY publishes branded endpoints for machine discovery and live preflight. The public-source preview is bounded static observation. Provider-backed outcome verification is not a current public API.

Read the current machine status as JSON →

Read the action-authority contract and examples →