NetworkCalc API
★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring Observabilitybearer9 EndpointsREST
For Agents
Resolve DNS records, WHOIS data, and SPF rules for a hostname, and persist saved queries on a NetworkCalc account.
Use for: Resolve the DNS records for example.com, Get the WHOIS for a domain, Validate the SPF record for our sending domain, Save this DNS lookup for later
Not supported: Does not handle authoritative DNS record management, DDoS protection, or email sending — use for DNS, WHOIS, and SPF lookups and saved-query retrieval only.
Jentic publishes the only available OpenAPI specification for NetworkCalc API, keeping it validated and agent-ready. NetworkCalc gives developers and network engineers a structured surface for DNS lookups, WHOIS registration data, and SPF record validation, plus persistence so saved queries and historical results can be referenced later. The nine-endpoint surface covers live DNS resolution, WHOIS, SPF parsing, and saved-query retrieval — handy for deliverability tooling, DNS dashboards, and ops automation.
Install Jentic One Beta
Connect the NetworkCalc API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the NetworkCalc API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with NetworkCalc API.
Resolve DNS A, AAAA, MX, TXT, and NS records for a hostname
Look up domain WHOIS registration and expiry data
Parse and validate an SPF record for an email-sending domain
Save a DNS, WHOIS, or SPF lookup for later retrieval
Retrieve a previously saved lookup by id
Build a deliverability dashboard powered by SPF and DNS data
Use Cases
Patterns agents use NetworkCalc API for, with concrete tasks.
★ Deliverability Pre-Flight
Before a marketing or transactional email send, validate the sending domain's SPF record and resolve its MX records to confirm the configuration is intact. NetworkCalc's SPF endpoint parses the record and surfaces include chains, hard-fail flags, and resolution counts so deliverability bugs are caught before they affect inbox placement.
Call /dns/spf/sender.example.com, return whether the record evaluates to softfail or hardfail, and list every include chain encountered.
DNS Operations Dashboard
Power an internal dashboard that resolves DNS for a list of customer-facing domains and saves the results for trend analysis. Pair the live lookup endpoint with the save endpoint so historical snapshots can be diffed when something breaks.
For each hostname in the customer list, call /dns/lookup/{hostname} and post the result to /dns/lookup/save/{hostname} for historical comparison.
Domain Expiry Alerting
Periodically pull WHOIS data for owned domains to detect upcoming expiries and registration status changes. Combine with a saved-query pattern to detect deltas between runs without re-pulling raw WHOIS each time.
Call /dns/whois/example.com, parse the expiry date, and raise an alert if expiry is within 30 days.
AI Agent Network Diagnostics
Let an AI agent answer questions like 'is example.com's MX record correct?' or 'when does this domain expire?' through Jentic. The agent calls the right NetworkCalc endpoint and returns a plain-English answer without the user dropping into terminal-based dig and whois commands.
Given the user question 'is acme.com's SPF set up correctly?', call /dns/spf/acme.com and return a one-paragraph plain-English summary.
Key Endpoints
9 endpoints — jentic publishes the only available openapi specification for networkcalc api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/dns/lookup/{hostname}
Resolve DNS records for a hostname
POST
/dns/lookup/save/{hostname}
Save a DNS lookup
GET
/dns/whois/{hostname}
Look up WHOIS for a domain
POST
/dns/whois/save/{hostname}
Save a WHOIS lookup
GET
/dns/spf/{hostname}
Parse and evaluate an SPF record
POST
/dns/spf/save/{hostname}
Save an SPF evaluation
GET
/dns/saved/{id}
Retrieve a saved lookup by id
GET
/dns/lookup/{hostname}
Resolve DNS records for a hostname
POST
/dns/lookup/save/{hostname}
Save a DNS lookup
GET
/dns/whois/{hostname}
Look up WHOIS for a domain
POST
/dns/whois/save/{hostname}
Save a WHOIS lookup
GET
/dns/spf/{hostname}
Parse and evaluate an SPF record
POST
/dns/spf/save/{hostname}
Save an SPF evaluation
GET
/dns/saved/{id}
Retrieve a saved lookup by id
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Your NetworkCalc bearer token is stored encrypted in the Jentic vault. Agents receive scoped access — the token never appears in the agent's prompt context or logs.
Intent-based discovery
Agents search by intent (e.g. 'resolve dns records') and Jentic returns the matching NetworkCalc operation against /dns/lookup, /dns/whois, or /dns/spf with its parameter schema, so the agent calls the right endpoint without docs.
Time to first call
Direct NetworkCalc integration: half a day to wire auth and parse responses. Through Jentic: under 30 minutes to search, load, and execute the first lookup.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using NetworkCalc API through Jentic.
Why is there no official OpenAPI spec for the NetworkCalc API?
NetworkCalc documents its API in narrative form on the NetworkCalc site but does not publish a downloadable OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call NetworkCalc API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the NetworkCalc API use?
NetworkCalc uses HTTP bearer token authentication on endpoints that touch saved queries. Public lookups can be called unauthenticated within rate limits. Through Jentic the token is stored encrypted and injected at execution time.
Can I save a DNS or WHOIS lookup with the NetworkCalc API?
Yes. POST /dns/lookup/save/{hostname}, /dns/whois/save/{hostname}, and /dns/spf/save/{hostname} persist a lookup against your account, and GET /dns/saved/{id} retrieves it later. Useful for trend analysis and audit trails.
What are the rate limits for the NetworkCalc API?
NetworkCalc enforces conservative per-IP limits on unauthenticated calls and higher limits on authenticated calls. The exact ceiling is not published per second; for production volume request authenticated quotas via the NetworkCalc account.
How do I validate an SPF record through Jentic?
Run jentic.search('validate spf record'), load the matching operation, and execute GET /dns/spf/{hostname} with the sending domain. Jentic returns the parsed record so the agent can summarise pass/fail and surface the include chain.
Does the NetworkCalc API resolve IPv6 (AAAA) records?
Yes. GET /dns/lookup/{hostname} returns A, AAAA, MX, TXT, and NS records in a structured payload. Filter the response client-side for the record type you need.
GET STARTED