USEFUL APIS FOR AI AGENTS

Calendar

Importable calendar files from event JSON.

Create RFC 5545 ICS calendars for appointments and itineraries, with all-day events, locations, descriptions and bounded recurrence. Timed events and recurrences are emitted in UTC; all-day end dates are exclusive.

0.02 USDCBase mainnetx402 v2

Make this part of your workflow.

One fixed example is free. Custom work uses a clear input contract and releases the result after payment settles.

Make a custom request · 0.02 USDC ↗Fixed free example ↗Interactive API reference ↗OpenAPI contract ↗Agent instructions ↗

One copyable request.

POST /v1/calendars/build

{
  "name": "Project milestones",
  "events": [
    {
      "title": "Launch review",
      "start": "2026-10-12T10:00:00-05:00",
      "end": "2026-10-12T10:45:00-05:00",
      "location": "Conference room A",
      "description": "Review the release checklist and support handoff."
    },
    {
      "title": "Planning day",
      "start": "2026-10-13",
      "end": "2026-10-14",
      "all_day": true
    }
  ]
}

Send the JSON to the operation above. An x402-capable client receives the payment challenge, authorizes exactly 0.02 USDC, and retries with PAYMENT-SIGNATURE.

Keep the result.

ICS + event manifest

Files arrive in a JSON artifact envelope with base64 bytes, filename, MIME type, size and SHA-256. Decode the bytes to save the file. Diagnostic results arrive as structured JSON.

The same proof and normalized input retrieves the exact paid result for 30 minutes across restarts. A proof cannot unlock another request. Never create another authorization automatically after ambiguous delivery.