PontyBot

PontyBot is the automated agent used by Ponty's recruitment platform for outbound requests to external sites — for example when job adverts are published to a customer's website. It is not a web crawler and it does not collect data; it only delivers content to systems that are integrated with Ponty.

How to identify our requests

Every request from Ponty carries this User-Agent. Only the PontyBot/1.0 prefix is stable — the service name and version vary, so match on the prefix:

PontyBot/1.0 (+https://ponty-system.se/bot; <service>; pcore/<version>)

Verifying our requests cryptographically

This is the method we recommend. PontyBot signs every outbound request using Web Bot Auth — Ed25519 HTTP Message Signatures (RFC 9421). Signed requests carry Signature, Signature-Input and Signature-Agent headers, and our public key is published as a JSON Web Key Set at:

https://ponty-system.se/.well-known/http-message-signatures-directory

The keyid in Signature-Input is the JWK thumbprint (RFC 8037) of the key in that directory. The directory response is itself signed with the same key, so it cannot be mirrored by a third party.

A signature proves who we are regardless of which address the request came from, and it keeps working if our networking ever changes. If your bot-protection service supports signature-based verification, use it in preference to the IP rules below.

Allowlisting by IP address

Where signature verification is not available, allowlist our fixed outbound IP address instead. All Ponty services publish from this single, unchanging address:

34.78.137.246

All of our requests originate only from the IPv4 address above; we do not send traffic over IPv6. A machine-readable list (one IP per line) is available at /bot/ips.txt.

Note that this address carries all of Ponty's outbound traffic, not only advert publishing, so an allowlist entry is broader than a signature check. We deliberately do not disguise our requests as a web browser, so where an IP rule is your only option it will work reliably.

Cloudflare

On Cloudflare the allowlist must be configured in Cloudflare itself — not on your origin server or site firewall. Our requests are stopped at Cloudflare's edge (typically by a Managed Challenge, Bot Fight Mode, or Super Bot Fight Mode) before they reach your server, so an origin-side rule has no effect. Because we are a server-to-server integration with no browser, we cannot solve a challenge — the request has to be allowed through instead.

We have applied to Cloudflare's Verified Bots programme using signature verification. Once PontyBot is listed, the rules below stop being necessary — verified traffic is recognised across every Cloudflare zone, including the platform-level protection used by managed WordPress hosts. Until then, the correct method depends on your Cloudflare plan.

Free plan (Bot Fight Mode)

Add our IP address as an IP Access Rule with the action Allow, targeting 34.78.137.246. Bot Fight Mode cannot be bypassed with a WAF custom rule — it runs outside Cloudflare's Ruleset Engine, so Skip and Allow custom-rule actions have no effect on it. A matching IP Access Rule is the only mechanism that stops Bot Fight Mode, so free-plan sites must use this method.

Pro, Business, and Enterprise (Super Bot Fight Mode)

The simplest option is still an IP Access Rule with the action Allow for 34.78.137.246. This stops Bot Fight Mode and Super Bot Fight Mode and exempts our traffic from Cloudflare's default protections.

However, an IP Access “Allow” rule does not reliably bypass WAF Managed Rules or a custom rule you have written with a Block action. If our requests are still blocked after adding the Allow rule, create a single WAF custom rule with the Skip action and place it first, above any rule that could block or challenge our traffic:

Expression:  (ip.src eq 34.78.137.246)
Action:      Skip
Skip:        All remaining custom rules, All managed rules,
             All rate limiting rules, All Super Bot Fight Mode rules
Place at:    First

Because custom rules are evaluated before Super Bot Fight Mode and Managed Rules, a Skip rule placed first deterministically covers every feature that runs on Cloudflare's Ruleset Engine. This is Cloudflare's recommended approach for trusted API and integration traffic. (Note: Cloudflare does not permit skipping IP Access Rules themselves.)

Enterprise with the Bot Management add-on

Bot Management scores every request via cf.bot_management.score instead of using Bot Fight Mode. Exclude our IP from your bot-score rule — for example, add and ip.src ne 34.78.137.246 to that rule's expression — or add the Skip custom rule described above.

Managed hosting platforms

Some hosting providers run their own Cloudflare in front of every site they host, so the controls above may live in the provider's dashboard rather than in a Cloudflare account you own. On WP Engine, for example, bot-category blocking is configured under Edge Traffic Rules in the User Portal, and anything beyond that has to be requested from the provider's support team.

If your provider asks which request was blocked, the error message shown in Ponty includes the Cloudflare Ray ID — that identifies the exact rule that fired.

Contact

Questions about PontyBot or an integration? Email support@ponty.se.