# 402utils ICS Calendar File Generator

> 402utils ICS Calendar File Generator is a paid API for AI agents from 402utils.com, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-12).

Generates a strictly RFC 5545-conformant .ics calendar file from a list of events, handling text escaping, line folding, UID generation, and UTC timestamps.

## Facts

- Endpoint: POST https://402utils.com/v1/ics?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/402utils-ics-calendar-file-generator-3bcd3f1e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Lsnbh-61sgUTlEaMa-3Q5

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 402utils-ics-calendar-file-generator-3bcd3f1e -d '<json body>'
```

Example prompt: Create an .ics calendar file for our team sprint planning: a recurring weekly meeting called 'Sprint Planning' every Monday at 10am Europe/Berlin starting 2025-02-03, ending at 11am, with location 'Conf Room A' and description 'Weekly sprint kickoff'.

## When to prefer this

Use this endpoint when you need a correctly spec-compliant .ics file without hand-rolling RFC 5545 escaping, UID generation, or UTC offset logic. Ideal for agents generating calendar invites, scheduling workflows, or exporting events for import into Google Calendar, Outlook, or Apple Calendar.

## Known failure modes

- Missing required 'title' or 'start' field on an event returns a 400 validation error
- Invalid IANA timezone string causes timestamp conversion failure
- Malformed RRULE passthrough may produce non-importable calendar entries
- More than 100 events in a single request exceeds the allowed array limit
- Payment not included or invalid results in a 402 Payment Required response

## How this service works

Build a strictly RFC 5545-conformant .ics calendar file from a list of events: correct TEXT escaping, 75-octet line folding, generated UIDs, and unambiguous UTC timestamps (a per-event IANA timezone interprets naive wall-clock times). Supports all-day events, location, description and a passthrough RRULE. The fiddly conformance an agent shouldn't hand-roll.

## Output

Returns a valid .ics (iCalendar) file with proper RFC 5545 formatting, including TEXT-escaped fields, 75-octet line folding, auto-generated UIDs, and unambiguous UTC DTSTART/DTEND timestamps. The file is ready to import into any calendar application.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "events": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "title",
     "start"
    ],
    "properties": {
     "end": {
      "type": "string"
     },
     "rrule": {
      "type": "string",
      "description": "RFC 5545 RRULE value, passthrough."
     },
     "start": {
      "type": "string",
      "description": "ISO date or date-time."
     },
     "title": {
      "type": "string"
     },
     "allDay": {
      "type": "boolean"
     },
     "location": {
      "type": "string"
     },
     "timezone": {
      "type": "string",
      "description": "IANA tz for naive times, e.g. Europe/Paris."
     },
     "description": {
      "type": "string"
     }
    }
   },
   "description": "Events (1–100)."
  },
  "calendarName": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": "BEGIN:VCALENDAR\r\nVERSION:2.0\r\n…\r\nEND:VCALENDAR\r\n"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/402utils-ics-calendar-file-generator-3bcd3f1e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from 402utils.com](https://www.zero.xyz/host/402utils.com/llms.txt)