Domains provisioned in one burst
provisioningDomains whose registration, first certificate and first DNS answer cluster inside a short window: the shape of infrastructure stood up in one go. NEEDS AN API KEY ON THE PRO PLAN.
max_hours_to_cert bounds registration to certificate and cert_to_dns_max bounds certificate to first answer, both in hours. first_dns_answer is bounded by our own scan latency, so within 24 hours of registration only some candidates have one yet; the reply's coverage says how many. tld, ns, since and until narrow it; page with after=<next_cursor>. A tight cluster is a pattern, not a finding.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "provisioning"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ns | No | Only domains delegated to this nameserver. | |
| tld | No | Only this TLD. | |
| after | No | The next_cursor from the previous call. | |
| limit | No | Rows per page. | |
| since | No | Window start, RFC3339 or YYYY-MM-DD, UTC. | |
| until | No | Window end, RFC3339 or YYYY-MM-DD, UTC. | |
| cert_to_dns_max | No | First certificate to first DNS answer, at most this many hours. | |
| max_hours_to_cert | No | Registration to first certificate, at most this many hours. | |
| include_cert_before_zone | No | Also include domains certified BEFORE a zone file listed them. |