APIVerve

Reach a curated set of APIVerve's utility APIs behind one key, covering conversion, validation, lookup, and generation tasks. Agents fill small gaps in a workflow without standing up a service for each one.

27 actions API key available

APIVerve website ↗ Platform Documentation ↗ Capability data verified 2026-07-31

A new vendor record reaches the onboarding queue

Agent pulls the tax ID, remittance email, and phone number off the submitted form

Agent runs Validate Tax ID, Validate Email Address, and Validate Phone Number against the submitted values

Agent compares the returned risk bands and the disposable-domain flag against the threshold for a new payee

Agent posts the masked tax ID and the per-segment validation detail to the accounts payable channel

The AP lead approves the payee or returns the record to the vendor for correction before any banking detail is stored

What This Integration Enables

Every serious workflow hits chores that sit between the systems that actually matter. A tax ID needs checking before a payee is created. A domain needs a WHOIS record pulled before a contract is signed. A page needs archiving as a PDF because compliance will ask what it said on a given day. None of these justify a vendor relationship of their own, and standing one up for each is how integration projects quietly die: six months in, the flow that was supposed to save the controller a day a week is blocked on procurement approval for a $9 phone validation API.

APIVerve exists to end that. It bundles hundreds of small utility APIs behind one key, and this connector exposes the curated set that automation actually reaches for. Four validators cover the fields that cause the most downstream damage. Five checks cover domains and links, four read a web page and two capture one, and the remainder handle currency, location, and short text work. The curation is the product. FlowRunner agents call these the way a person reaches for a calculator, mid task, without leaving the Flow conversation and without a new contract. And when a check comes back ambiguous rather than clean, the agent does not average it out. It raises an automation exception and puts the call in front of the person who owns the consequence.

Without FlowRunner

Fields accepted as typed A vendor's tax ID, email, and phone enter the ledger exactly as they were keyed, correct or not

Checks deferred to failure The typo surfaces when a payment bounces or a 1099 is rejected, months after onboarding

A tool per check Each validation is a separate vendor contract, a separate key, and a separate line on the renewal list

With FlowRunner

Screened at intake Format, deliverability, and numbering plan are checked before the record is written

Failures raised as exceptions A tax ID that fails segment validation becomes a queued decision, not a silent write

One credential for the set Validation, domain checks, capture, and lookup all run behind a single connection

Use Case Scenarios

Screening a payee before the ledger is touched

A vendor completes an onboarding form. Before the record reaches the accounting system, the agent runs Validate Tax ID on the submitted number, which reports whether the value is an SSN, EIN, or ITIN, returns a masked form safe to log, and flags well known placeholders such as 123-45-6789. It runs Validate Email Address on the remittance contact, which distinguishes a corporate domain from free consumer mail and from a known disposable provider, and flags role accounts. It runs Validate Phone Number against the country's numbering plan and reports whether the line is mobile, VOIP, or fixed. Clean submissions post. Anything that fails, or that comes back in a risk band the finance team has not agreed to accept, stops and waits.

Watching the domains a business depends on

A scheduled flow walks the list of domains a company owns and the domains of its top vendors. For each, the agent runs Check SSL Certificate for the validity window and whether the certificate is expired or self signed, Lookup DNS Records to confirm mail servers and an SPF record are still published, and Lookup WHOIS Record for the registrar, expiry date, and domain status codes. A certificate approaching expiry or a name server that changed without notice becomes a ticket with the evidence attached rather than an outage nobody predicted.

Capturing what a page said, on the day it said it

A compliance workflow needs proof of a supplier's published terms at the moment an order was placed. The agent calls Convert Website To PDF and Capture Website Screenshot, both of which save their output to FlowRunner file storage and return a durable link rather than APIVerve's expiring signed URL. It runs Extract Page Text to pull the readable prose with navigation and boilerplate stripped, then Summarize Text so a reviewer can see what changed without reading the whole page. The artifact and the summary are attached to the order record together.

Human-in-Loop Highlight

The gate sits on Validate Tax ID, and it is there because the failure is not a data quality problem. A tax ID that fails per-segment validation means one of two things: someone fat-fingered a digit, or the entity about to be set up as a payee is not the entity it claims to be. APIVerve returns the evidence for both readings and refuses to choose between them, which is the correct behavior for a validator and the wrong behavior for a payment. So the agent stops. It posts the masked tax ID, the last four digits, the identified type, the per-segment detail, and the risk score to the accounts payable channel, and asks: "Vendor Northlake Fabrication submitted an EIN that fails segment validation. Correct the number with the vendor, or reject the onboarding?" Nothing is written to the vendor master, no banking detail is stored, and no first payment is scheduled until a person answers. This is human-in-the-loop doing the one job a validator cannot: deciding what a failed check means.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

27 actions

Validation

Validate Email Address Checks format validity, MX record presence, and whether the domain is free consumer mail, corporate, or a known disposable provider, and flags role accounts such as info@ or support@. Used to screen signup forms and lead lists before a send or a CRM write.
Validate Phone Number Validates a number against a country's numbering plan and returns the detected country, line type, disposable-range status, and the number in international, national, E.164, and RFC 3966 forms. Used to gate SMS sends and clean contact records.
Validate Credit Card Runs a Luhn checksum and brand pattern match, returning the brand, BIN, last four digits, expected CVV length, and whether the number is a known test card. This is offline structural validation only and does not contact the issuer.
Validate Tax ID Validates a US taxpayer identification number, identifies whether it is an SSN, EIN, or ITIN, and returns normalized, digits-only, and masked forms plus per-segment detail. Used at vendor and payee intake, where a bad number surfaces months later as a rejected filing.

Domain Intelligence

Check Domain Availability Reports whether a domain is unregistered, and names the current registrar when it is taken. Used to screen candidate names in bulk during brand work.
Check SSL Certificate Inspects the TLS certificate a domain serves and returns subject, issuer, alternative names, key size, and validity window, plus derived checks for expiry and self-signing. Used in scheduled domain health sweeps.
Lookup DNS Records Resolves A, AAAA, MX, NS, SOA, and TXT records for an apex domain and summarizes whether mail servers and an SPF record are present. Used to verify mail configuration before a sending program starts.
Lookup WHOIS Record Retrieves registrar, creation and expiry dates, status codes, DNSSEC state, name servers, and abuse contacts, with derived domain age. Used in vendor diligence and fraud screening.
Unshorten URL Follows a shortened link through its full redirect chain and returns the final destination, the destination domain, and every hop. Used to reveal where an inbound link actually goes before an agent or a person follows it.

Web Content

Scrape SEO Data Fetches a page and returns its full SEO profile, including title, meta description, canonical URL, robots directives, Open Graph and Twitter tags, and JSON-LD blocks. Used for site audits and competitor monitoring.
Extract Page Metadata Returns the lighter metadata set for a page: title, description, canonical URL, language, charset, author, favicons, and structured data. Used when a flow needs a link preview rather than an audit.
Extract Page Text Returns the main readable article text with navigation, scripts, and boilerplate removed, alongside the detected title and publication date. Used to feed clean prose into a summarization or classification step.
Scrape Page Links Collects every hyperlink with its anchor text, resolved href, and off-site flag, plus internal and external counts and the unique destination domains. Used for broken-link sweeps and outbound link review.

Web Capture

Capture Website Screenshot Renders a page in a headless browser at a chosen viewport and format, and saves the image to FlowRunner file storage so the link outlives APIVerve's expiring signed URL. Used for visual change tracking and evidence capture.
Convert Website To PDF Renders a page to a paginated PDF and stores it durably in FlowRunner file storage. Used to archive published terms, pricing, and policy pages against a date.

Location and Data

Lookup IP Address Resolves an IPv4 or IPv6 address to country, region, city, postal code, coordinates, IANA timezone, accuracy radius, and EU membership. Used for routing, fraud screening, and regional compliance branching.
Reverse Geocode Coordinates Converts a latitude and longitude pair into the nearest postal address components, with the distance to the closest match and nearby city names. Used to turn device pings and form geolocation into readable places.
Lookup Timezone Returns local date and time for a location with UTC offset, Unix timestamp, weekday and month names, and daylight saving state including transition dates. Used to schedule sends and calls in the recipient's working hours.
Get Current Weather Returns current conditions including temperature, wind, pressure, precipitation, and visibility in both metric and imperial units. Used in field service and logistics flows that branch on conditions.
Get Exchange Rate Returns the current rate between two ISO 4217 currencies along with the inverse, so a flow can convert in either direction without a second call. Used in quoting and pricing steps.

Text

Summarize Text Produces an extractive summary by selecting the most representative sentences and reports the original word count, summary word count, and percentage reduction, up to 5000 characters per call. Used to compress captured page text before a human reads it.
Analyze Sentiment Returns a raw score, a comparative score normalized by word count, a plain-language label, and positive and negative flags. Used to prioritize inbound messages rather than to answer them.
Translate Text Translates into a target ISO 639-1 language and returns the resolved source and target codes, with optional auto-detection of the source. Used to normalize multilingual inbound text before routing.
Detect Language Identifies the most likely language with a confidence level and a ranked list of candidates. Used to route multilingual enquiries to the right queue.
Filter Profanity Detects profanity and returns a cleaned version with offending words masked, plus a flag and a count. Used as a first pass on user-generated content before it reaches a public surface.

Generation

Generate QR Code Generates a QR code for a URL, email address, phone number, or other supported payload, with control over size, margin, colors, and dot styling, saved to FlowRunner file storage. Used for tickets, labels, and printed collateral produced inside a flow.
Generate Passwords Generates one or more random passwords at a chosen length and complexity, returning each with its length and complexity metadata. Used in provisioning flows that create temporary credentials.

Frequently Asked Questions

What can FlowRunner do with APIVerve?

FlowRunner agents can run Validate Email Address, Validate Phone Number, and Validate Credit Card in APIVerve, plus 24 more actions.

Does connecting APIVerve to FlowRunner require OAuth?

No. APIVerve connects to FlowRunner with an API key, no OAuth flow required.

Can APIVerve trigger a FlowRunner workflow automatically?

APIVerve doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with APIVerve

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us