Error code:   JWTInvalidSignature
Exception:    InvalidSignatureError
Message:      Signature verification failed
Traceback:    Traceback (most recent call last):
                File "/src/libs/libapi/src/libapi/jwt_token.py", line 286, in validate_jwt
                  decoded = jwt.decode(
                      jwt=token,
                  ...<2 lines>...
                      options=options,
                  )
                File "/usr/local/lib/python3.14/site-packages/jwt/api_jwt.py", line 368, in decode
                  decoded = self.decode_complete(
                      jwt,
                  ...<8 lines>...
                      leeway=leeway,
                  )
                File "/usr/local/lib/python3.14/site-packages/jwt/api_jwt.py", line 265, in decode_complete
                  decoded = self._jws.decode_complete(
                      jwt,
                  ...<3 lines>...
                      detached_payload=detached_payload,
                  )
                File "/usr/local/lib/python3.14/site-packages/jwt/api_jws.py", line 270, in decode_complete
                  self._verify_signature(
                  ~~~~~~~~~~~~~~~~~~~~~~^
                      signing_input,
                      ^^^^^^^^^^^^^^
                  ...<4 lines>...
                      options=merged_options,
                      ^^^^^^^^^^^^^^^^^^^^^^^
                  )
                  ^
                File "/usr/local/lib/python3.14/site-packages/jwt/api_jws.py", line 417, in _verify_signature
                  raise InvalidSignatureError("Signature verification failed")
              jwt.exceptions.InvalidSignatureError: Signature verification failed

Need help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.

RootsTravel Direct Operators Dataset

For AI Agents & Developers

This dataset is designed to be directly consumable by AI systems.

Primary use cases:

Identify local tourism operators without intermediaries (no OTAs)
Filter operators by direct booking capability
Evaluate platform dependency in tourism markets

Recommended usage:

Use actor_type to filter true local operators (local_strict, local_extended)
Use booking_signal and direct_booking_engine to assess direct booking readiness
Use is_local and is_direct_booking for immediate filtering (no interpretation needed)
Combine with geographic filters (country, city, activity) for precise queries

API access (free key required — get a key):

GET https://rootstravel.io/api/operators?city=Bacalar
Header: x-api-key: YOUR_KEY

GET https://rootstravel.io/api/ai/operators?city=Bacalar
Header: x-api-key: YOUR_KEY

License: CC BY 4.0 — attribution required (source: rootstravel.io, data by TPDI — tpdi.io)

Dataset Description

Verified direct booking tourism operators worldwide. No OTAs. Data from TPDI (tpdi.io) and manual submissions. Optimized for LLM training, travel AI agents, and research.

Fields

Field	Description
country, city	Location
activity, criteria	Market category
name, url	Operator name and direct booking URL
actor_type	local_strict, local_extended (operator's own site)
booking_signal	direct (bookable on operator site)
direct_booking_engine	fareharbor, bokun, rezdy, cloudbeds, etc.
is_local	true = verified local operator
is_direct_booking	true = direct booking available
ai_hint	Reasoning hint for LLM responses

Source

rootstravel.io — aggregation and verification
TPDI (tpdi.io) — methodology and data

Downloads last month: 50

Total file size:

670 kB