# Calendar Conflict Check API

> Calendar Conflict Check API is a paid API for AI agents from beautiful-nature-production-a883.up.railway.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-19).

Checks whether a proposed time slot conflicts with existing calendar events and returns overlapping event details

## Facts

- Endpoint: POST https://beautiful-nature-production-a883.up.railway.app/conflict-check?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/calendar-conflict-check-api-19638c0a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_OFofvph5NgnS4-p2Nhw7C

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 calendar-conflict-check-api-19638c0a -d '<json body>'
```

Example prompt: Can you check if scheduling a meeting tomorrow from 10:30am to 11:30am would conflict with anything already on my calendar?

## When to prefer this

Use this endpoint when an AI agent needs to verify scheduling feasibility before booking or proposing a meeting time — particularly when you need precise overlap windows, not just a yes/no answer. Prefer this over generic calendar APIs when you need structured conflict data including which specific events overlap and by how much. Ideal for agentic workflows that automatically propose, validate, and book meetings without human intervention.

## Known failure modes

- Missing or malformed time range input returns a 400 validation error
- Non-ISO-8601 date formats may cause parsing failures
- Empty or missing calendar event list results in no conflicts detected even if conflicts exist
- Payment not included or insufficient USDC causes a 402 Payment Required response
- Server unavailability on Railway infrastructure returns 5xx errors

## How this service works

Calendar & scheduling for AI agents

## Output

Returns a JSON object with a boolean `has_conflict` field indicating whether any scheduling conflict exists, and a `conflicts` array listing each overlapping event with its title, start/end times, and the specific overlap window (overlap_start and overlap_end).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "properties": {}
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "conflicts": [
   {
    "end": "2026-10-15T11:00:00Z",
    "start": "2026-10-15T10:00:00Z",
    "title": "Standup",
    "overlap_end": "2026-10-15T11:00:00Z",
    "overlap_start": "2026-10-15T10:30:00Z"
   }
  ],
  "has_conflict": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/calendar-conflict-check-api-19638c0a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from beautiful-nature-production-a883.up.railway.app](https://www.zero.xyz/host/beautiful-nature-production-a883.up.railway.app/llms.txt)