transfer.schedule

Schedule a future-dated transfer.

Schedule a future-dated transfer. Envelope is evaluated at schedule time AND again at execute time; policy bumps between the two can still deny the scheduled transfer.

Metadata

Field	Value
Name	transfer.schedule
Category	write
Required scope	payments:initiate
Idempotency key required	yes

Annotations

Annotation	Value
Title	Schedule Transfer
Read-only	no
Destructive	no
Idempotent	yes
Open-world	no
Requires human approval	no

Input schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "counterparty": {
      "type": "object",
      "properties": {
        "address": {
          "type": "string",
          "minLength": 1
        },
        "chain": {
          "type": "string",
          "enum": [
            "eth",
            "base",
            "arb",
            "op",
            "polygon",
            "sol"
          ]
        },
        "token": {
          "type": "string",
          "minLength": 1
        }
      },
      "required": [
        "address",
        "chain",
        "token"
      ],
      "additionalProperties": false
    },
    "amount_cents": {
      "type": "integer",
      "minimum": 0,
      "maximum": 9007199254740991
    },
    "currency": {
      "type": "string",
      "minLength": 1,
      "maxLength": 8
    },
    "execute_at": {
      "type": "string",
      "format": "date-time",
      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$"
    },
    "memo": {
      "type": "string",
      "maxLength": 280
    },
    "idempotency_key": {
      "type": "string",
      "minLength": 8,
      "maxLength": 128
    }
  },
  "required": [
    "counterparty",
    "amount_cents",
    "currency",
    "execute_at",
    "idempotency_key"
  ],
  "additionalProperties": false
}

Output schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "scheduled_transfer_id": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    },
    "execute_at": {
      "type": "string",
      "format": "date-time",
      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$"
    },
    "policy_version_at_schedule": {
      "type": "integer",
      "minimum": 0,
      "maximum": 9007199254740991
    },
    "enqueued_at": {
      "type": "string",
      "format": "date-time",
      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$"
    }
  },
  "required": [
    "scheduled_transfer_id",
    "execute_at",
    "policy_version_at_schedule",
    "enqueued_at"
  ],
  "additionalProperties": false
}

Auth

Caller’s grant must include the payments:initiate scope. Grants whose scope set is a superset of the required scope are accepted.

Request examples

curl

curl -X POST https://mcp.glide.co/mcp/write \
  -H "Authorization: Bearer $GLIDE_GRANT_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: sched-payroll-2026-05-15-acme" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "transfer.schedule",
    "params": {
      "counterparty": {
        "address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
        "chain": "base",
        "token": "USDC"
      },
      "amount_cents": 250000,
      "currency": "USD",
      "execute_at": "2026-05-15T09:00:00Z",
      "memo": "May payroll — Acme contractor",
      "idempotency_key": "sched-payroll-2026-05-15-acme"
    }
  }'

Response examples

Accepted (below step-up threshold)

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "scheduled_transfer_id": "a3b4c5d6-e7f8-4a9b-8c0d-1e2f3a4b5c6d",
    "execute_at": "2026-05-15T09:00:00Z",
    "policy_version_at_schedule": 7,
    "enqueued_at": "2026-05-04T14:22:33Z"
  }
}

Step-up required (amount over envelope threshold)

{
  "jsonrpc": "2.0",
  "id": 1,
  "error": {
    "code": -32003,
    "message": "scheduled transfer of 250000 cents requires step-up approval before it can be enqueued",
    "data": {
      "reason_id": "step_up_required",
      "step_up_url": "https://app.glide.co/step-up/confirm?sigil=eyJhbGci..."
    }
  }
}

Errors

Code	reason_id	Meaning
-32000	unauthenticated	Bearer token missing or expired.
-32001	unauthorized	Grant does not include payments:initiate.
-32002	policy_denied	Envelope denied the scheduled amount (velocity, allowlist, daily cap, etc.).
-32003	step_up_required	Amount meets the step-up threshold. Follow the integration’s approval flow; this input schema does not accept step_up_sigil.
-32004	rate_limited	Too many schedule requests. data.retry_after_seconds tells you when to retry.
-32602	execute_at_not_future	execute_at is not strictly after the current time.
-32602	execute_at_beyond_horizon	execute_at is more than 90 days from now.
-32603	internal_error	Transient server fault. Retry with the same idempotency key.

Step-up flow

The handler evaluates the envelope before enqueueing a schedule. If the amount is at or above step_up_amount_cents and the other checks pass, it returns -32003 with an approval URL instead of enqueueing.

The current input schema has no step_up_sigil field, and this handler does not redeem an approval token. Do not add that field and assume the schedule was approved. The configured integration must provide the continuation; if it does not, scheduling remains blocked.

A successfully queued schedule still depends on execution-time policy checks and a working scheduler. Track its recorded status rather than treating execute_at as a settlement guarantee.