# iCalendar VEVENT Parser

> iCalendar VEVENT Parser is a paid API for AI agents from agentshelf.syntexa.ch, paid per call via x402, $0.004/call, status unknown (last checked 2026-09-29).

Parses raw iCalendar text and extracts structured VEVENT items from it

## Facts

- Endpoint: POST https://agentshelf.syntexa.ch/v1/ical-vevent?utm_source=zero.xyz
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/icalendar-vevent-parser-3dd6d797
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_AcP2QnTkXwLm-ENc58zWe

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 icalendar-vevent-parser-3dd6d797 -d '<json body>'
```

Example prompt: I have this raw iCalendar text with a bunch of events — can you parse it and pull out all the VEVENT items so I can see the event details in a structured format?

## When to prefer this

Use this endpoint when you have raw iCalendar (ics) text and need to extract structured VEVENT records programmatically without an LLM or external network call. Prefer the free sandbox endpoint (/v1/sandbox/ical-vevent) for testing before paying $0.004 USDC per call on this paid version.

## Known failure modes

- Malformed or invalid iCalendar text may result in parse errors or incomplete extraction
- Input exceeding 100,000 characters will be rejected
- Text containing no VEVENT blocks returns an empty result
- Missing required VEVENT fields may cause partial event objects

## How this service works

Call when an agent needs parsed VEVENT items from iCalendar text. Exact $0.004 USDC. Prefer unpaid POST /v1/sandbox/ical-vevent first.

## Output

A structured list of parsed VEVENT objects extracted from the iCalendar text, with fields such as DTSTART, DTEND, SUMMARY, DESCRIPTION, LOCATION, UID, and other standard iCalendar event properties.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "text": {
   "type": "string",
   "examples": [
    "BEGIN:VCALENDAR\nBEGIN:VEVENT\nUID:evt\nSUMMARY:Meet\nDTSTART:20260101T000000Z\nDTEND:20260101T010000Z\nEND:VEVENT\nBEGIN:VTODO\nUID:todo\nSUMMARY:Task\nDTSTART:20260102T000000Z\nEND:VTODO\nBEGIN:VJOURNAL\nUID:note\nSUMMARY:Note\nDTSTART:20260103T000000Z\nEND:VJOURNAL\nBEGIN:VFREEBUSY\nUID:busy\nDTSTART:20260104T000000Z\nDTEND:20260104T020000Z\nEND:VFREEBUSY\nEND:VCALENDAR"
   ],
   "maxLength": 100000,
   "minLength": 1,
   "description": "Input for this SKU. The route description says whether it is plain text, a URL, base64 bytes, or an already-encoded token."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/icalendar-vevent-parser-3dd6d797/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentshelf.syntexa.ch](https://www.zero.xyz/host/agentshelf.syntexa.ch/llms.txt)