Tool search 101,857 tools · 5,224 live servers

Book a hotel room using a rate from get_hotel_details. Requires a Gondola account (API key) and a saved payment method. Use get_payment_methods to find your payment ID. The gondola_rate_id comes from the room rates returned by get_hotel_details — each room option has a rate ID you can use here. Guest details (given_name, family_name, email_address, phone_number) can either be passed directly or prefilled from a saved travel profile: pass travel_profile_id (from get_travel_profiles) to book "as <traveler>" without collecting each field. Any field you also pass explicitly overrides the profile. To earn points and elite credit, pass loyalty_account_id — use the Member Number from get_loyalty_accounts that matches the hotel's chain (e.g. the World of Hyatt account for a Hyatt property). When a loyalty_account_id is passed, the booking goes out under the email registered to that membership (overriding any travel profile or email_address), so the stay credits to the right account. Args: gondola_rate_id: The rate ID from get_hotel_details room rates. payment_id: Payment method ID from get_payment_methods. given_name: Guest's first name (optional if travel_profile_id is provided). family_name: Guest's last name (optional if travel_profile_id is provided). email_address: Guest's email for confirmation (optional if travel_profile_id is provided). phone_number: Guest's phone number with country code (optional if travel_profile_id is provided). special_request: Optional special request for the hotel (e.g. "high floor", "late check-in"). loyalty_account_id: Optional Member Number (from get_loyalty_accounts) to earn points. travel_profile_id: Optional travel profile ID (from get_travel_profiles) to prefill guest details. Returns: Booking confirmation with ID and details, or an error message.

Create a rate alert to monitor a hotel for price drops. Set up an alert to be notified by email when the rate drops for a specific hotel. Optionally specify dates, or leave them out to monitor any stay. Requires a Gondola account with an API key. Args: hotel_id: The hotel's Vervotech property ID (from search results). checkin: Check-in date in YYYY-MM-DD format. Must be provided with checkout, or both omitted. checkout: Check-out date in YYYY-MM-DD format. Must be provided with checkin, or both omitted. Returns: Confirmation that the rate alert was created, with notification details.

Book a rental vehicle from a search result. Requires a Gondola account (API key) and a saved payment method. Use get_payment_methods to find your payment ID. Args: search_id: Search ID from search_vehicles. vendor_code: Vendor code from search results (e.g. "ZE" for Hertz). rate_code: Rate code of the selected vehicle from search results. acriss_code: ACRISS vehicle classification code from search results. given_name: Renter's first name. family_name: Renter's last name. email_address: Renter's email for confirmation. phone_number: Renter's phone number with country code (e.g. "+1-555-123-4567"). payment_id: Payment method ID from get_payment_methods. pickup_location: Optional pickup IATA code for the selected vehicle (disambiguates metro fanouts). loyalty_account_id: Optional loyalty account ID to earn points on this rental. Returns: Booking confirmation with ID and details, or an error message.

Get the user's saved travel profiles (guest name, email, and phone presets). Each profile has a selectable Profile ID. Pass it to book_hotel as `travel_profile_id` to prefill the guest details — the same "book as <traveler>" selection the website checkout offers — instead of collecting name, email, and phone field by field. Requires a Gondola account (API key). Returns: Formatted list of travel profiles with IDs, or instructions to add one.

[Public] Register a new agent. Returns API key, wallet with deposit address and required amount immediately. Email verification is optional but required to access user profiles.

[Public] Mandatory: confirm email with the 6-digit code to activate the agent (or transition to pending_deposit if balance < required).

[Public] Resend email verification code.

Returns the Smarter Weather developer request-access URL (with MCP referral attribution). The developer platform is in limited preview: signup is invite-based. Present the URL to the user so they can request access in a browser; once they receive and accept an email invitation, they authenticate this MCP server via OAuth to continue onboarding (key minting, client configuration). No authentication required.

Get your user a free Aimnis API key (no credit card, takes one call). Ask your user for their email address first. The key comes back in this tool result — relay it to the user so they can save it and add it to your MCP connection ('Authorization: Bearer aim_...'). A key raises the daily live-search limits; cached answers are always free, with or without a key. Re-registering with the same email rotates (replaces) that email's key.

Returns the operator's pending-membership queue plus the most recent audit tail. Each pending record: { user_id, email, display_name, current_tier, requested_tier, note, submitted_at }. Each audit entry: { user_id, email, action ('approve'|'deny'|'auto-promote'|'request'|'demote'), from, to?, requested?, reason?, by_clerk_user_id?, at }. Use BEFORE ic_admin_approve_tier_request / ic_admin_deny_tier_request to see who's waiting and why. Args: none. Required scope: admin:tier_review.

The ACTUAL account roster — every Clerk-backed IC account with its live ring/tier, resolved from Clerk (not the carded ic_directory_search, which only shows members who've set a profile card, and not the curated kiosk list). This is what you want to answer 'who are the members' or find a specific account (e.g. one that hasn't set a card yet). Each member: { user_id, name, email, tier ('public'|'ft-member'|'ai-floor'|'ic-member'|'operator'), pending_request (the tier they've requested but not yet been granted, or null), created_at }. Args: { tier?: filter to one ring; q?: case-insensitive name/email/user_id substring filter; limit?: number (default 200, max 500); offset?: number (default 0) }. Filters apply to the fetched page; `total` is the full Clerk account count and `has_more` tells you to page with offset (default limit covers all IC accounts in one page today). Required scope: admin:tier_review.

Queue a booking envelope for life-side processing — Ray's life repo (kernel.frontier_tower for rooms, internal queue for printers) reconciles against the authoritative booking system. Returns 'queued', not 'confirmed.' Rate-limited 10/token/UTC day; 30-day dedupe on (resource_id, user, start_iso). Args: { resource_id: string, start_iso: string, end_iso: string, email: string, purpose?: string }. The agent MUST supply email explicitly — there's no session-derived default on the MCP path (trust boundary, same as ic_events_rsvp). Required scope: resources:book.

Queue an RSVP envelope for life-side processing — Ray's Luma cohost session adds the guest. This returns 'queued', NOT 'Luma confirmed.' The human will get a Luma email on the next processor cycle. Rate-limited to 10/token/UTC day; idempotent via 7-day dedupe on (event_url, user). Args: { event_url: string, email: string, name?: string }. The agent MUST supply email explicitly — the server doesn't derive it for agent callers (trust boundary). Required scope: events:rsvp.

Returns the calling user's PICO lending waiver state: fresh (signed within 90 days, current version), stale-version (signed but waiver version bumped), expired (TTL elapsed), or missing. Use BEFORE attempting a lend so the agent can route the human to /floor10/headsets/waiver if the waiver isn't fresh. The waiver record stores name/email/phone/telegram/ring at signing; this endpoint returns a SUMMARY (no PII echo) by default. Args: none. Returns: { state: 'fresh'|'stale-version'|'expired'|'missing', version?, signed_at?, expires_at? }. Required scope: headsets:read.

Returns the calling user's currently-active PICO lend, or null if they have none. Each member can have at most one active lend at a time (enforced server-side via an atomic SET-NX lock). Use this to answer 'am I currently borrowing a headset?'. Args: none. Returns: { lend: LendRecord | null }. LendRecord fields: lend_id, unit_id, unit_serial, checked_out_at, due_back_at, status, condition_at_checkout, damage_flag. PII fields (email/telegram) are stripped on the MCP path. Required scope: headsets:read.

List members of the community, with pagination. Optionally filter by a search term (`query`, matches name/username/email), by role (`roleIds`), order (`orderBy`), and reverse. Returns edges[].node (with role) plus pageInfo and totalCount. Bettermode GraphQL query: members.

Get a single community member by their `id`. Returns name, username, email, status, creation date, role, and tagline. Bettermode GraphQL query: member.

Find the single best-matching person profile for a set of identifying attributes (name, email, phone, profile URL, company, etc.). Returns one record plus a likelihood score (1-10), or a 404 'no match' body. Use uniquely-identifying inputs for best results. API: GET /person/enrich.

Create a proactive monitoring subscription to a live-data event stream. Returns the new subscription id. Requires a Pipeworx OAuth account (anonymous + BYO cannot persist subscriptions). Supported types: "sec_8k" (8-K filings matching ticker + item codes — e.g. items:["5.02"] = officer change), "polymarket_edge" (Polymarket↔Kalshi cross-venue mispricings — params:{topic:"fed"}), "fred_series" (new FRED observations — params:{series_id:"UNRATE"}). Delivery channels: feed (always on — pull via recent_alerts or GET registry.pipeworx.io/alerts.json), and optionally email (set delivery:{email:"you@x.com"}) or sms (delivery:{sms:"+15551234567"} — phone must be verified at /account first; 10/day cap).

Creates a user account with the given email, sends a verification email, and returns an API token. Unverified users are limited to 30 queries/month; verified users can make 300/month for free. Drop us an email to tell us how you found the service and if you want more queries (see website footer)

Send an inquiry on behalf of the user to the advertiser of a listing, a development project, or a real-estate company. Notifies them (email + WhatsApp) and starts a conversation. Works without an account. This sends a real message to real people — confirm the details with the user before calling.

Attach a real email address to the signed-in user's phone-keyed TuLugar account (accounts created via WhatsApp have no usable email). Sends a confirmation link TO that email; the user must open it — the link proves they own the address. Ask for the email, confirm it back to them, then call this. Only works for accounts that do not have a real email yet; if the email belongs to another account, the tool explains the options (never merges silently).

Reply to a buyer inquiry (lead) on one of the agent's listings. Compose a helpful, professional reply as `message`, and this returns a one-tap WhatsApp link (wa.me) to the buyer with your message pre-filled — share that link with the agent to tap and send. Pass inquiry_id from my_inquiries. If the buyer left only an email, it returns the email to reply to instead.