Calendar to JSON | Vextorium
Paid API · api.vextorium.com · found in a public registry · checked since 2026-10-17
Live, payment required · latest check
POST https://api.vextorium.com/v1/ics-to-json$0.002 per call · from the registry's payment termsThe name is the registry's label, not ours. Not reviewed by a person. See 1052 endpoints from vextorium.com.
Our checks
An unpaid request daily, from eastern North AmericaLast 1 checks, oldest to newest; room for 29 more
1 passed, 0 failed, 29 not run.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
Details
Payment terms
- Price per call
- $0.002
- Protocols
- x402
- Networks
- solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdpeip155:8453eip155:137eip155:10eip155:5042xrpl:0
- Terms changes, 90 days
- 0 in 2 days tracked
Price from the registry's payment terms; protocols and networks from its payment request at our checks. Current terms first seen 2026-10-17; 0 receiving-address changes. Definitions
Reported by the registry
- Payers, 30 days
- 4
- Paid calls, 30 days
- 4
The registry's own figures, not our measurements.
Listing
In the capability tree: Business and productivity / Calendars and scheduling (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/3, tree/3) on 2026-10-18. Wrong place? Tell us.
In the index only: does not meet every one of our listing criteria (listing-criteria/3): ✓ says what it does; ✓ its latest check passed; ✗ fewer than 5 payers in 30 days (registry figure).
Purpose tags: calendaricaleventsschedulingparsing
Recent probes
| When | Result | Networks offered | Time to headers |
|---|---|---|---|
cloudflare:ATL |
Live, valid payment request HTTP 402 | solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdpeip155:8453eip155:137eip155:10eip155:5042xrpl:0 | 433 ms |
What these figures do not show
- A passing probe means the endpoint answered an unpaid request with a valid payment request on a production network (x402 on a mainnet network, or MPP on Tempo mainnet). It does not show that a paid call succeeds or returns useful results.
- Payer and call counts are the registry's own figures, not our measurements.
- The registry's description is not republished.
- Limited evidence: monitored for 1 day (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_afe3114b99711da5