Book an intro call with powers.now

Three quick questions, then pick a time. You get a confirmation with a calendar invite. powers.now runs Lead Scheduler, hosted by powers.now: use it on this page, or let your AI assistant read it and hand you a link.

Next openings (12)

Times are in America/New_York.

48 more in the live view below and at api/slot.

Booking

Reference: POW-NQMZY9GJ · Slot: slot-20261102T130000Z · Monday, Nov 2, 8:00 AM EST · Monday, Nov 2, 8:30 AM EST · Lead: lead · Status: confirmed · Calendar: durable · Calendar event: booking-slot-20261102T130000Z · Friday, Oct 30, 4:45 PM EDT · Confirmed by: user · Notification: queued · Summary: Mon, Nov 2, 8:00 AM EST · 30 min

Questions we ask

What does your business do?
Which power interests you?: Lead Scheduler / Booking / Listings / Skill Router / Champ Workspace / Not sure yet
Your website (optional)
Your name and email

How to complete without a connector

Open this page with the choice and answers in the link; the page pre-fills them for the visitor to review and confirm. Deep-link grammar:

Example: https://powers.now/book/?slot=slot-20261102T134000Z&name=%3Cname%3E&email=%3Cemail%3E

Every parameter is optional and URL-encoded. Unknown parameters are ignored; invalid values are dropped and the page still opens.
Values are validated against the power’s schema (text length, listed options, numbers) before anything is pre-filled.
Pre-fills land in the user lane: the visitor reviews them on the page and confirms there. A deep link never completes an action by itself.
Selecting a record (slot) applies the same change the visitor would make by picking it, so the page lands on the confirm step.

For AI assistants

Read API (GET only, JSON, CORS enabled; nothing changes state over GET): https://powers.now/book/api/

https://powers.now/book/api/state: The whole current snapshot as the embed reads it: revision, status, every record, runs and the enabled actions.
https://powers.now/book/api/lead: Your request: the current record. The visitor’s contact details and qualifying answers, with who filled each field. The CRM-ready lead record.
https://powers.now/book/api/slot: Openings: the current records (append /<id> for one record). Openings from powers.now’s calendar for the next 14 days, 30 minutes each. Patch status to "held" to reserve one for 10 minutes; patch it back to "open" to release.
https://powers.now/book/api/booking: Booking: the current record. The confirmed slot with its calendar event, the lead reference and the notification state. Written only by the confirm action.
https://powers.now/book/api/openings ?from&to&weekdays&part&timeZone&limit: Openings that match a preference, in the visitor’s zone and powers.now’s zone (America/New_York), each with the deep link that pre-selects it on the website.
https://powers.now/book/api/export: The CRM-ready lead record of this session as a CSV line (with header) and as the webhook JSON body.

Guide: https://powers.now/book/llms.txt. Manifest: https://powers.now/book/.well-known/power.json.

To act for the visitor, give them a deep link (above). On Claude, you can also fetch the fragment https://powers.now/book/fragment.html, prefill LEAD_SCHEDULER_DEFAULTS with what you read here labeled as example data, and render it as an HTML artifact: its actions become deep links to this page.

Hosts that support MCP Apps can connect https://powers.now/book/mcp (Streamable HTTP) and show the live card inline. In the visitor’s own browser, the embed on this page registers WebMCP page tools when document.modelContext or navigator.modelContext exists.