# Palmyr Compute Server Execute

> Palmyr Compute Server Execute is a paid API for AI agents from palmyr.ai, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-13).

Executes a command or workload on a specified compute server instance via the Palmyr autonomous infrastructure platform.

## Facts

- Endpoint: POST https://palmyr.ai/compute/servers/%7Bid%7D/exec
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/palmyr-compute-server-execute-2c8847d5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tuR76vNgkuyphGa46WL5N

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability palmyr-compute-server-execute-2c8847d5 -d '<json body>'
```

Example prompt: Run my data processing script on Palmyr compute server abc123 — execute the job and return the output.

## When to prefer this

Use this endpoint when you need to execute a command or workload on a specific Palmyr-managed compute server instance, paying per-call with USDC via x402 on Solana or Base. Prefer this over general cloud providers when operating within an autonomous AI agent workflow that requires crypto-native micropayment infrastructure.

## Known failure modes

- Server ID not found — 404 if the specified server ID does not exist or is not accessible
- Payment failure — 402 if USDC payment on Solana or Base is insufficient or rejected
- Execution error — 500 if the command fails on the server side
- Invalid request body — 400 if the execution payload is malformed
- Timeout — if the compute job exceeds allowed execution duration

## How this service works

Autonomous infrastructure for AI agents — pay with USDC on Solana or Base via x402.

## Output

Returns the result of the executed command or workload on the specified server instance, as a JSON payload. The response schema is minimal and example-based, so the agent should treat the returned object as the raw execution output.

## Request schema (JSON Schema)

```json
{
 "properties": {
  "input": {
   "properties": {
    "body": {
     "type": "object",
     "additionalProperties": true
    }
   }
  },
  "output": {
   "properties": {
    "example": {
     "type": "object",
     "additionalProperties": true
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "example": {}
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/palmyr-compute-server-execute-2c8847d5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from palmyr.ai](https://www.zero.xyz/host/palmyr.ai/llms.txt)