The suspect seems to be good at covering their tracks — some of our systems have missing periods in their logs. However, the culprit seems to have forgotten about our S.P.I.D.E.R. protocol (Super Private IDentity Emergency Recall), which triggered when they tried to access confidential data about Agent Web.

Your task: Check the S.P.I.D.E.R. logs through its API to verify what agents have recently triggered the protocol.

S.P.I.D.E.R. API Endpoints:

• GET /api/v1/spider/info - System information
• POST /api/v1/spider/key - Obtain API key
  Body: {"agent_id":"investigation_team","clearance":"omega"}
• GET /api/v1/spider/agents?query="<name>" - Search agents by name
• GET /api/v1/spider/logs/<UUID> - View agent access logs

Unfortunately, the culprit was successfully able to corrupt our suspect tracking system. Luckily we have partners with the W.E.B. (Worldwide Evidence Bureau) that can monitor our suspects by UUID.

The data has been stored in the Base64 format, likely to save space. It's up to you to connect to the W.E.B.'s API, retrieve the data for each suspect, and decode it to determine suspicious transactions (denoted with "suspicious": true) involved in the crime.

W.E.B. API Endpoints:

• GET /api/v1/web/info - System information
• GET /api/v1/web/suspects - List all suspects under surveillance
• GET /api/v1/web/surveillance/<uuid>?page=<N> - Paginated surveillance logs (Base64 encoded)