DEV Community: ambolt

Check SSL certificates and domain expiry for a whole list of domains

ambolt — Sun, 04 Oct 2026 08:00:00 +0000

An expired certificate or a lapsed domain takes a site down at the worst time, and it is almost always avoidable. If you look after more than a handful of domains, the useful question is not "what are the details for each?" but "which ones need attention this month?".

One request

curl "https://api.ambolt.dev/v1/domain-ssl-sweep?domain=sitemaps.org&warnDays=30&free=1"

The answer has a summary and one result per domain:

{
  "checked": 1,
  "readable": 1,
  "flagged": 0,
  "warnDays": 30,
  "results": [
    {
      "domain": "sitemaps.org",
      "ok": true,
      "ssl": {
        "issuer": "Microsoft Corporation",
        "notAfter": "2026-12-07T04:56:13.000Z",
        "trusted": true,
        "daysLeft": 64,
        "expired": false
      },
      "registration": {
        "registered": true,
        "expiresAt": "2027-08-12T23:51:55Z",
        "daysToExpiry": 313,
        "registrar": "MarkMonitor Inc.",
        "nameservers": ["ns3-02.azure-dns.org", "ns1-02.azure-dns.com"]
      },
      "flags": []
    }
  ]
}

Recorded 2026-10-03; fields trimmed. flags stays empty until something expires inside the window you set with warnDays, so a scheduled job only has to look at flagged and the flags.

A whole list

Pass domains with a list instead of domain, or run the Apify Actor on a schedule and send the flagged rows to your alerting. You are billed per domain checked; a domain that cannot be reached is listed with the reason and not charged.

What it does not return

Registrant details are never returned. SSL data comes from the certificate the server presents, and domain data from the registry's RDAP service, so a registry that does not publish an expiry date shows no date rather than a guess.

See the catalog for the tool and its price.

PDF and DOCX to Markdown and tables, without an LLM

ambolt — Sat, 03 Oct 2026 17:46:48 +0000

Language models can read documents, but they give a different answer on a different day and charge by the token. For invoices, reports and contracts that you process in volume, a deterministic parser is often the better tool: the same file gives the same output, and the price does not depend on how long the answer is.

DocToJSON reads PDF and DOCX files from a public URL and returns three things.

Markdown with structure

Headings and lists become Markdown. Text keeps the order it has on the page.

Tables as data

Every table is returned as rows and as CSV, so it can go straight into a sheet or a database.

Named fields

You can pass hints such as invoice number, date or total. The tool finds a value by its label and returns it together with the line it came from. A field that is not found is reported as not found, never guessed.

Scans

Scanned pages are read with OCR (Tesseract). The output warns you on every page where OCR was used, because text from a scan deserves a second look.

Honest limits

Merged cells, multi-line headers and unusual layouts can need checking.
Image-only pages give nothing unless OCR can read them.
Files are fetched for the run and not kept beyond the platform's own run storage.

Price

It is billed per page, with a higher price for OCR pages, and failed files are not charged. Run it as an Apify Actor; see the DocToJSON page for inputs, outputs and current prices.

EU and UK public tenders in one schema, with OCDS export

ambolt — Sat, 03 Oct 2026 17:16:41 +0000

Public tenders are published in several places with different fields. If you track them for a product, a bid team or an agent, you end up writing a parser per source. TenderFeed returns one record shape for TED (the EU's journal) and the UK's Find a Tender service; SAM.gov can be added with your own key.

One request

curl "https://api.ambolt.dev/v1/tender-feed?keyword=software&country=DEU&free=1"

The answer starts with what each source did, then the notices:

{
  "publishedSince": "2026-09-26",
  "sources": [
    { "source": "ted", "ok": true, "totalMatches": 285, "returned": 20 },
    { "source": "uk-fts", "ok": true, "totalMatches": 0, "returned": 0 }
  ],
  "count": 20,
  "notices": [
    {
      "id": "ted:681459-2026",
      "source": "ted",
      "title": "Germany – IT services: consulting, software development, Internet and support – …",
      "buyer": "Robert Koch-Institut, Beschaffung",
      "buyerCountry": "DE",
      "cpv": ["72000000"],
      "noticeType": "can-standard",
      "publishedAt": "2026-10-02",
      "url": "https://ted.europa.eu/en/notice/-/detail/681459-2026",
      "licence": "TED reuse: acknowledge source"
    }
  ]
}

Recorded 2026-10-03; fields trimmed. Fields a notice does not publish, such as the deadline or the estimated value, come back as null rather than guessed.

What you can filter on

Keyword, CPV prefix, country and a start date, so a scheduled run only sees what is new. An OCDS 1.1 release package is available if your system already speaks that format.

What it does not return

Contact persons and e-mail addresses are removed, descriptions included. The feed does not return supplier or award data.

Where to get it

As an HTTP endpoint with x402 (per call), as an Apify Actor on a schedule, and as daily alerts in Telegram. Details, sources and licences are on the TenderFeed page.

Resolve a company to its official record with one call

ambolt — Sat, 03 Oct 2026 17:06:43 +0000

A company name in a form field is not an identity. "Equinor" could be the listed group, a subsidiary or a toastmasters club that shares the address. Before an agent enriches, scores or onboards anything, it needs the legal entity from the official register.

One request

curl "https://api.ambolt.dev/v1/entity-resolve?query=Equinor%20ASA&country=NO&free=1"

The answer is the best match plus candidates, each with the register it came from:

{
  "matched": true,
  "bestMatch": {
    "country": "NO",
    "registry": "Brønnøysundregistrene (Enhetsregisteret)",
    "registryId": "923609016",
    "name": "EQUINOR ASA",
    "legalForm": "Allmennaksjeselskap",
    "status": "active",
    "incorporationDate": "1972-09-18",
    "lei": "OW6OFBNCKXC4US5C7523",
    "sourceUrl": "https://data.brreg.no/enhetsregisteret/api/enheter/923609016",
    "licence": "NLOD 2.0",
    "matchScore": 100,
    "matchReason": "exact normalised name"
  }
}

Recorded 2026-10-03; fields trimmed. The record carries sourceUrl and licence, so you can show where a fact came from and under which terms it may be reused.

What goes in

A company name, a website domain, a registry number, an LEI or a VAT number. The tool works out which one it got.

Where it looks

The official registers of Norway, Finland, Czechia, Slovakia, France and the United Kingdom, Poland by KRS number, and any company with an LEI worldwide through GLEIF. Each register is queried directly; each record names its licence.

What it does not do

It returns companies only: no officers, directors or owners, and no sole traders (their names are personal data).
Scores under 90 are suggestions. Check the linked source record before acting on them.
It does not replace an official extract or your own KYB process.

Using it

As an MCP tool: add https://api.ambolt.dev/mcp to your agent and call entity_resolve (free, 30 requests a minute).
As an HTTP endpoint: a price in the 402 answer, paid in USDC with an x402 client. Add free=1 for one free call per tool and IP address per day.
As an Apify Actor with batches of up to 100.

See the EntityResolve page for inputs, sources and prices.

How an agent pays per call with x402

ambolt — Sat, 03 Oct 2026 17:06:17 +0000

Most data APIs want an account, a key and a monthly plan. An agent that needs one answer once does not want any of that. x402 turns the HTTP status code 402 ("Payment Required") into a payment step that a program can complete on its own.

The flow

The client sends a normal request, for example GET /v1/iban-validate?iban=….
Without payment the server answers 402 with the price and the payment options in a header: network, asset (USDC) and the receiving address.
The client signs a payment for exactly that amount and sends the request again with the payment attached.
The server checks the payment, runs the call and returns the result. If the call fails, nothing is charged.

On Base and Polygon the client needs a little USDC and no gas token: the wallet signs an authorisation for the exact amount and a payment service submits it. Solana is also supported.

Try it without a wallet

Add free=1 and the call is free once per tool and IP address per day:

curl "https://api.ambolt.dev/v1/iban-validate?iban=DK5000400440116243&free=1"

Without it you get the 402 answer with the price, which shows the protocol without paying anything.

From code

The JavaScript and Python clients wrap every endpoint as a method and work with any x402-capable fetch.

import { createAmbolt } from '@ambolt/sdk';
const ambolt = createAmbolt({ fetch: payingFetch });
console.log(await ambolt.ibanValidate({ iban: 'DK5000400440116243' }));

Prices start at $0.003 a call. The full list is in the catalog, and every tool is also available as a free MCP tool at https://api.ambolt.dev/mcp.