fetch-seatengine-token

To retrieve the legacy SeatEngine APP_AUTH_TOKEN from the old cart bundle, use this deprecated Skill. It accesses the old cart bundle data without introducing runtime dependencies, relying on static frontmatter metadata for discovery.

The deprecated SeatEngine token verification process involves fetching the APP_AUTH_TOKEN from the old cart bundle. After retrieval, the token must be checked with /check-seatengine-token to ensure it remains valid for current workflows.

No, the SeatEngine token fetcher does not introduce runtime dependencies. It relies entirely on static frontmatter metadata for discovery and operation within the legacy checkout workflow.

You can fetch the old SeatEngine checkout token, but it is explicitly marked as deprecated. You must verify its current status using /check-seatengine-token to confirm it is still valid before relying on it.

Your legacy SeatEngine authentication token may no longer work because the old cart bundle process is deprecated and unsupported. You must run a verification check using /check-seatengine-token to confirm the token validity.

You should not use the fetch-seatengine-token Skill for new integrations because it is deprecated. It is only intended for legacy verification workflows where the old widget was relied upon, directing users to /check-seatengine-token.