Display
Find

Find your next step

Filter public starting points, or search the full product catalog.

Public starting points

8 shown
Browse all resources Escape closes Find
Share

Share this public page

Gateway Information Group

Focused checks / Useful results

Make your next step
a little clearer.

Prepare text, check data against your rules, or trace the effects of a change. Each tool has a defined scope and a private result.

See a fictional example report →

A focused tool.
A clear scope.

Prefer to pay with a wallet?

Checking wallet choices…

HTTP Retry-After Compliance Audit API

Audit supplied Retry-After header occurrences against exact received and follow-up observations.

Audit supplied Retry-After header occurrences against exact received and follow-up observations. Preserve every field occurrence in retryAfterValues; use an empty array only when the field was absent. Observations use whole-second YYYY-MM-DDTHH:mm:ssZ UTC in years 0001–9999. One nonnegative decimal seconds value, including leading zeroes, or a strict IMF-fixdate resolves an exact earliest follow-up time. Surrounding HTTP optional space or tab is ignored only for interpretation. Multiple occurrences are ambiguous; a present empty field is invalid. A past date requires zero remaining wait from receipt. The observed wait remains signed when follow-up precedes receipt, which is too early for any resolved instruction. Obsolete RFC850/asctime dates, leap seconds and exact results beyond year 9999 are unsupported-profile, rather than claims of invalid historical HTTP-date syntax. IMF-fixdate weekday and calendar values are checked. This bounded RFC 9110 sections 10.2.3 and 5.6.7 profile does not execute retries, choose retry policy, contact a server, parse wire messages or establish full historical HTTP-date conformance. Use authorized, non-sensitive data. The report describes supplied records and does not change external systems.

Agent API guide → · Website orders show the report on your private order page.

The complete checkout request must fit within 40,000 UTF-8 bytes. Your input is validated again before an order is created.

Before you begin

Use non-sensitive information you are authorized to process. Do not include passwords, wallet keys, personal records or confidential material. Examples stay in your browser until you submit checkout.

Payment options appear only when available for your selected service. Confirmed payment starts processing. Save your private order link to retrieve the JSON result during its 30-day access period. These checks do not establish factual accuracy, regulatory compliance or complete dependency coverage.

Purchase terms and support · Privacy policy