API · x402 · early usage

Create RFC 5545 ICS calendars for appointments and itineraries, with all-day events, lo…

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.

by calendar-api-production-33a1.up.railway.app · discovered, not yet claimed by its owner · updated 2026-10-09

30d calls3

30d payers2

MethodPOST

Outputjson

Mirrored from Coinbase's public x402 Bazaar. The description is the provider's own text and has not been reviewed here; the payment requirements are copied as published.

What it does

Tags: bazaar

Call contract

Method: POST
Input: json
Output: json
Last paid call: 2026-10-09

Input example from Bazaar metadata

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

No output exampleProvider did not publish one in Bazaar metadata.

Use with an agent

Discover. Agents find this listing with GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP tool search_resources, or /discovery/resources.
Inspect. Fetch /resources/57381.json for the price and payment options.
Pay. Call GET https://calendar-api-production-33a1.up.railway.app/v1/calendars/build. The provider answers 402 with its payment requirements. An x402 client signs one of the options below and retries with PAYMENT-SIGNATURE.
Execute. The provider returns 200 with the data. Agent Bazaar is not in the request path and never sees your payment.

For humans

You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.

Pricing & payment

Price: $0.02 / request
Protocol: x402 v2
Auth: No account or API key. Pay per request.
Networks: Base
Demand: 3 calls · 2 unique payers in 30d (public x402 Bazaar data)

x402 payment requirements

Scheme	Network	Asset	Amount	Pay to	Timeout
exact	Base eip155:8453	USDC	$0.02	0x5461f103b54fcFE37a99337D3cb5AB5d30239c18	300s

accepts[] (raw JSON)

[
  {
    "scheme": "exact",
    "network": "eip155:8453",
    "payTo": "0x5461f103b54fcFE37a99337D3cb5AB5d30239c18",
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "amount": "20000",
    "amountUsd": 0.02,
    "maxTimeoutSeconds": 300
  }
]

Examples

curl

curl "https://calendar-api-production-33a1.up.railway.app/v1/calendars/build"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paid

JavaScript

const res = await fetch("https://calendar-api-production-33a1.up.railway.app/v1/calendars/build");
if (res.status === 402) {
  const { accepts } = await res.json();
  // pay one of accepts[] via an x402 client, then retry with the payment header
}

Python

import httpx
res = httpx.get("https://calendar-api-production-33a1.up.railway.app/v1/calendars/build")
if res.status_code == 402:
    accepts = res.json()["accepts"]
    # pay one of accepts[] via an x402 client, then retry with the payment header

Details

Provider: calendar-api-production-33a1.up.railway.app
Endpoint: https://calendar-api-production-33a1.up.railway.app/v1/calendars/build
Machine-readable: /resources/57381.json