slotflow.dev valid

Slotflow

Slotflow is scheduling infrastructure for AI agents. It provides a REST API that lets AI agents check availability, book appointments, and manage the full booking lifecycle for real humans — without breaking the agent workflow.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T10:01:04.102Z. Cached copy · Source on slotflow.dev

# Slotflow

> Slotflow is scheduling infrastructure for AI agents. It provides a REST API that lets AI agents check availability, book appointments, and manage the full booking lifecycle for real humans — without breaking the agent workflow.

Slotflow is built for developers building AI agent products: sales automation, recruiting automation, customer support escalation, and AI assistants that need to schedule humans. It is not a calendar app or a Calendly competitor. It is infrastructure — the scheduling layer that sits inside an AI agent's workflow.

## Key Pages

- [Homepage](https://slotflow.dev/)
- [Pricing](https://slotflow.dev/#pricing)
- [Sign up](https://app.slotflow.dev/)
- [Documentation](https://docs.slotflow.dev/)
- [Quickstart](https://docs.slotflow.dev/guides/quickstart)
- [API Reference](https://docs.slotflow.dev/api-reference)

## Documentation

Full API reference for agents: https://slotflow.dev/llms-full.txt
Documentation root: https://docs.slotflow.dev/

## What Slotflow Does

- Provides a REST API authenticated via API key
- Developers create "humans" in the system — real people whose time can be booked
- Developers set availability rules per human: working days, working hours, meeting durations
- Developers set schedule overrides: block time off (vacations, recurring meetings), add extra availability (overtime, weekend shifts) — supports date ranges, time windows, and recurring patterns
- AI agents call GET /v1/humans/:id/slots to retrieve available time slots
- AI agents call POST /v1/bookings to confirm a booking
- Slotflow fires webhooks on booking.confirmed and booking.cancelled events
- Agents pass metadata through bookings to keep their workflows connected

## Core API Endpoints

- GET /v1/humans/:id/slots — get available slots for a human
- POST /v1/bookings — create a booking
- DELETE /v1/bookings/:id — cancel a booking
- POST /v1/humans — create a human
- PUT /v1/humans/:id/availability — set availability rules
- POST /v1/humans/:id/overrides — create schedule override (block or open)
- GET /v1/humans/:id/overrides — list schedule overrides

## Use Cases

- AI sales agent that autonomously books demo calls with sales reps
- AI recruiting tool that schedules interviews without human intervention
- AI customer support that escalates to a human and books a callback
- AI assistant that manages a human's appointment calendar

## Pricing

- Free: $0/month — 100 bookings, 1 human
- Starter: $79/month — 1,000 bookings, 5 humans
- Growth: $299/month — 10,000 bookings, 25 humans
- Enterprise: contact sales

Overage packs available on paid plans: $19 per 500 additional bookings.

## SDKs

- **Node.js / TypeScript**: `npm install slotflow` — [npm](https://www.npmjs.com/package/slotflow) — [docs](https://docs.slotflow.dev/node-js-sdk)
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=slotflow.dev · GET /v1/domain/slotflow.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for slotflow.dev:
1. POST https://agentwebmap.com/v1/sites/slotflow.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://slotflow.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/slotflow.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/slotflow.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.