Tool search 164,478 tools · 10,067 live servers

Create a rate alert to monitor a hotel for price drops. The user will be notified by email when the rate drops. Optionally specify dates, or leave them out to monitor any two-night stay.

Get details for a hotel booking made through Gondola, using the Gondola booking ID shown as "Gondola booking" by get_upcoming_trips and get_past_trips. Returns hotel name, dates, room type, rate, status, and cancellation policy. A hotel or airline confirmation number will not resolve. Reservations Gondola imported from email have no Gondola booking ID; get_upcoming_trips and get_past_trips already return their full detail, so answer from those instead of calling this.

Get the user's past hotel stays and flights. Use this to answer travel-history questions and make recommendations grounded in behavior (e.g. "you loved the Park Hyatt last year", "you've flown United six times this year", "what seats have I taken before?", or "what is my favorite airplane seat?"). Returns past hotels and flights with dates, confirmation numbers, status, costs, loyalty programs, routes, airlines, ticket class, miles redeemed, and historical flight seat assignments when Gondola parsed real row+letter seats from airline emails. Opens with a Patterns block summarising the WHOLE history (aisle/window/middle seat mix, airline share, top routes, hotel chains, recorded spend), then one page of individual reservations newest first. For favorite-seat, aisle/window, side-of-plane, seat-letter, or preferred-row questions, read the Patterns block rather than tallying rows yourself, and do not say seat data is unavailable until this tool has been checked. Pass page=2, 3, ... to walk further back through the reservation list.

Get the user's saved travel profiles — guest name, email, and phone presets. Each profile has a selectable ID you can pass to book_hotel as travel_profile_id to prefill the guest details, mirroring the website checkout where the user picks a saved traveler instead of typing each field. Use this before booking so you can offer "book as <traveler>" in one step.

Get the user's upcoming hotel, flight, and rental car reservations. Use this to ground recommendations in real plans (e.g. "your Tokyo trip is May 15-20, want me to find restaurants?"), check upcoming confirmation numbers, or answer what flights/cars/hotels are already booked. Returns dates, confirmation numbers, status, costs/rates, loyalty programs and earnings, savings/AutoSave signals, flight segment details, ticket class, miles redeemed, refundability/cancellation timing, and seat assignments when Gondola has parsed real row+letter seats from airline emails.

Start monitoring a hotel points booking for price drops. Checks daily and sends email alerts when the points rate decreases. Paid feature.

Log a hotel booking to the user's portfolio — award (points, with price-drop monitoring) or cash (paid with money; set kind:"cash" and original_pay_rate_usd). Use hotel_id from search_hotels / get_hotel_availability results. Pass trip_id to file the stay under a workspace Trip so it shows grouped with the matching flights. Works great with Gmail — pull check-in/out dates, room type, rate and confirmation number from the reservation email. Paid feature.

Log a flight booking/redemption — award (points) or cash (paid with money; set kind:"cash" and cash_paid). For multi-leg trips (connecting flights, open-jaw, return), call this once per leg using the same trip_id — put the total cost on the first leg and 0 on subsequent legs. Works great with Gmail — extract booking details from confirmation emails. Paid feature.

Create a saved route monitor. ATF checks every 6 hours for award seats matching the route + window + cabin and emails when fresh availability appears. Free accounts get one monitor; Premium is unlimited.

Save a recurring instruction ATF runs for the user unattended, then emails the result. Use for anything the user wants checked repeatedly without asking — e.g. 'every Sunday check whether LHR-NRT business opens on any programme I hold points for' or 'each morning tell me if any of my tracked bookings dropped in price'. Write `prompt` as a complete, self-contained instruction: it runs with no conversation history, so name the routes, programmes, cabins and dates explicitly. Premium only.

Email a user's confirmed feedback or bug report to Award Travel Finder support. Use this when the user explicitly wants to report a bug, share feedback, request an improvement, or report an incorrect AI result. Collect a concise summary and details first; for bugs, collect reproduction steps and expected/actual behaviour when possible. Only send after the user confirms the summary, or has clearly asked you to send the complete report. Never use this for ordinary travel questions.

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).

Audit ANY URL for AI-search readiness only (AEO/GEO/LLMO) — how likely ChatGPT, Claude, Perplexity & Google AI are to cite it. Checks ~7 AI-citation signals (FAQ/structured-data/entity schema, citable stats, llms.txt, author/E-E-A-T, OG). Returns a weighted 0–100 AI-readiness score + top fixes. Takes a `url`. Use full_seo_audit for the broader SEO picture, or get_my_store_audit for the user's own connected store. Returns a summary of the top issues; the complete written report is available via email_seo_report.

Crawl-audit ANY URL across the WHOLE SEO surface (no login needed): the AI-search signals PLUS on-page SEO (title/meta/headings/content), technical SEO (HTTPS, robots.txt, XML sitemap, canonical, mobile), and — for Shopify stores — product/offer/review/breadcrumb schema and image-alt coverage. Returns a weighted 0–100 score + top issues. Takes a `url`. This audits an arbitrary website by crawling it — for the user's OWN connected store with real analytics, use get_my_store_audit. Returns a summary of the top issues; the complete written report is available via email_seo_report.

ALWAYS OFFER THIS after running an audit: the audit tools return a summary of the top issues, while this sends the complete written report — every check, its evidence, and the fix in priority order. Ask the user which email address to send it to; never guess or reuse an address they did not give in this conversation. Email the full written SEO/AEO report for an audit this session already ran. Takes the audit_id returned by ai_search_diagnostic or full_seo_audit, plus the user's email. ONLY use an email address the user explicitly gave you - never guess or invent one. Offer this after presenting audit results.

Start an inxy subscription — autopilot SEO/AEO for Shopify stores (reads GSC/GA4/Merchant Center, plans a month of content, writes and publishes articles with schema, fixes meta/alt-text, and attributes revenue to content). Plans from $19/mo with a free trial. Returns a personalised signup link; payment and store connection complete in the browser. Optionally pass the user's `email` and `store_url` (ONLY if the user explicitly provided them - never invent either) so the team can follow up.

Pre-transaction risk screening for a domain, company or email domain: DNS resolution, MX presence, SSL validity/expiry, domain age via RDAP, website reachability. Returns risk score 0–100, risk level, per-check results and evidence. Run it before an agent pays, emails or integrates with an unknown party. Pay-per-call via x402 (USDC, Base).

Complete DNS inspection in one call over DNS-over-HTTPS: A, AAAA, MX, TXT, NS, CNAME, SOA and CAA records with TTLs — plus a derived email posture analysis (SPF present and policy, DMARC present and policy, MX count, overall assessment) that raw lookup tools don't do. Pay-per-call via x402 (USDC, Base).

Email address deliverability and risk check before sending: syntax, domain, MX records, SPF, DMARC, disposable-provider detection and role-account detection. Returns a 0–100 deliverability score, risk level and per-check details. Live DNS, no mailbox pinging. Pay-per-call via x402 (USDC, Base).

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).

Submits an enquiry to Executive Search Fees — NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquiry_fields) and consent=true; it validates and returns a summary, the consent line and a confirmation token — show the person the summary and the consent line. Step 2: only if the person agrees, call again with the same answers, consent=true and the confirmation token; the enquiry is then submitted, and the person receives an email with a link they must click before any provider sees it. Consent means the person has read and agreed to: "Happy for my details to go to relevant executive search firms, who'll contact me directly."

Register a new AgentPub agent and get an API key. Call this FIRST if you do not already have an AgentPub API key. Every other tool needs one; without this tool an MCP client had no way to obtain one, because registration is an HTTP POST and the connector only carries a key it was already given. You need two things from the person running you, and you must ask rather than invent either: - **owner_email**: their real address. It records who is accountable for what you publish, and the verification link goes there. It is encrypted, never displayed publicly, and stripped from every public API response. - **accept_terms**: their explicit authorisation to accept https://agentpub.org/terms on their behalf. This is a binding acceptance. You are the author of anything you publish — papers carry your display_name, there is no human byline, and every paper is permanently labelled AI-generated. The returned api_key is shown ONCE and cannot be retrieved again. Save it, and pass it as the `token` argument to other tools (or set AA_API_KEY). You can submit papers immediately. Papers stay private until the owner confirms their email — a paper that passes peer review is held as `accepted` and becomes public when the address is verified.

Request a free API key by email Step 1 of self-serve signup — no key required. Sends a one-time link to `email`; always returns 202 with the same accepted:true body whether or not that address already has a key (prevents account enumeration). **For agents helping a human get set up:** this endpoint is the only step you can call directly. The next step — opening the emailed link and clicking "Reveal my key" on `GET /v1/auth/verify` — **requires a real human click and cannot be automated or done on the human's behalf.** This is intentional: it's what stops email security scanners (e.g. Microsoft Safe Links) from silently consuming the link before the person ever sees it. Tell the human: check your email, open the link, click the button, then paste the key back here. **Not a pollable async job.** This 202 has no `Location`/`job_id` to poll — the next step is a human clicking an emailed link, not a machine checking a status endpoint. ### Responses: **202**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "accepted": true, "detail": "Detail" } ```

Crawl a website and extract emails, phone numbers, and social profiles. Args: website: The website URL to crawl (e.g. "example.com" or "https://example.com"). max_pages: Maximum number of pages to crawl (1-20).

Enrich a company: registry record + discovered contacts in one payload. Resolves the firm's ONRC record (identity incl. its registered website), crawls that website for emails / phones / socials, and returns the company detail plus quality-labelled contacts (each with a confidence and source) in a single call. Results are cached durably (keyed by the crawled domain) so re-crawling the same site is avoided. Args: cui: Romanian tax identification number (CUI), e.g. "2816464". website: Optional website override. When omitted, the firm's registered website is used (falling back to an error if none is on file). max_pages: Max pages to crawl (1-20).

Perform WHOIS + DNS + SPF/DMARC lookup for a domain. Args: domain: Domain name to look up (e.g. "example.com"). include_dns: Include DNS records (A, MX, NS, TXT, etc.). include_security: Include SPF/DMARC email-security check.

Send a Request-for-Quote to a manufacturer on behalf of the person you are helping — no account needed. ASK YOUR PRINCIPAL FOR THEIR NAME AND EMAIL FIRST and pass exactly what they give you; never invent an address. The manufacturer receives the request, and your principal receives a sign-in link by email where the reply and the supplier's contacts appear. Use this once they have chosen a supplier and want prices, samples or terms.

Record a buyer or producer you are talking to as a lead, which the platform then delivers to the Gemalli CRM. ASK THE PERSON FOR THEIR NAME, EMAIL AND PHONE — the sales team needs all three, and the platform rejects a lead missing any of them. Pass exactly what they give you; never invent contact details. Send an operation_id so a retry after a dropped connection does not create a duplicate. Returns the lead id.

Post a job on Himalayas without an account. Provide your email and company details. Payment is required — a Stripe checkout URL will be returned. No authentication needed.

[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.

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.

Set ENS resolver records for a name you own. Returns encoded transaction calldata ready to sign and broadcast. Supports: address records — ETH as a plain 0x address, non-ETH coins (BTC, SOL, LTC, DOGE, …) as the raw wallet-format address (bc1…, base58, …) which is ENSIP-9-encoded automatically; text records (avatar, description, url, social handles, AI agent metadata); contenthash as an ipfs:///ipns:// URI or bare CID (auto-encoded) or a pre-encoded 0x value; ENSIP-25 agent-registration records; and ENSIP-26 agent context and endpoint discovery. Always pass addresses and CIDs EXACTLY as the user gave them — never reconstruct or abbreviate them. Multiple records are batched into a single multicall transaction to save gas. Common text record keys: avatar, description, url, email, com.twitter, com.github, com.discord, ai.agent, ai.purpose, ai.capabilities, ai.category. ENSIP-25 support: Pass agentRegistration with registryAddress and agentId to automatically set the standardized agent-registration text record. This creates a verifiable on-chain binding between your ENS name and your agent identity in an ERC-8004 registry. ENSIP-26 support: Pass agentContext to set the agent-context text record (free-form agent description). Pass agentEndpoints with protocol URLs (mcp, a2a, oasf, web) to set agent-endpoint[protocol] discovery records.

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).

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).

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.

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 or update the authenticated user's registrant (WHOIS) contact — the name/address/phone/email a domain registry requires to complete a registration or marketplace-domain transfer. Call this when a tool reports error 'registrant_contact_required'. All fields are required except state and organization (state only where applicable). This does NOT charge anything. If a contact already exists, this UPDATES it with the fields you pass — always send the full current set of fields, not just the ones that changed.

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).

Transmet une demande de contact au propriétaire d'une location (id renvoyé par search_rentals). IMPORTANT : avant d'appeler cet outil, obtenir la confirmation explicite de l'utilisateur pour (1) l'envoi de la demande et (2) la transmission de ses coordonnées (nom, email, téléphone éventuel) au propriétaire, puis passer user_confirmed=true. Le propriétaire répond ensuite directement à l'utilisateur par email — mise en relation sans commission, AUCUNE réservation ferme ni paiement via cet outil. Le message personnel (min. 30 caractères) doit être rédigé avec l'utilisateur.

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).

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.

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)

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).

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).

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).

WHAT: Public NAP — mobile, landline, fax, email, mapsEmail (info@maps.ikeytz.com), WhatsApp, address, office coords. walkIn=false. USE for call/WhatsApp/mail CTAs. DOES NOT open tickets or send messages. NEXT: compose_tel_mobile, compose_whatsapp, compose_mailto, list_whatsapp_options.

WHAT: maps footer links (Hub, MCP-Hub, MCP, mapsEmail mailto, Urheberrecht, Copyright, Impressum-Kontakt) plus www HTML legal links (no price corpus). RETURNS maps[], html_www[], email, mapsEmail. USE for footer/legal discovery. NEXT: get_legal, compose_mailto.

WHAT: mailto:info@ikeytz.com plus mapsEmail info@maps.ikeytz.com (mapsHref). Call with {}. USE for email CTAs. DOES NOT send mail. NEXT: get_contact, list_footer.

Registers a prospective buyer's interest with the Ocean Builders sales team. Requires the buyer's real name and email (with their consent to be contacted); the team follows up by email. Returns a neutral acknowledgment.