BassBase API Integration

This tool lets the worker call the BassBase REST API using HTTP_Execute to either ingest tracks or retrieve track lists. Inputs are: op (string enum 'ingest' or 'get'), payload (string containing JSON to parse), and apiKey (string Bearer token). When op is 'ingest', the payload JSON must contain track fields: title, audio_url, category, source_id, duration, license, attribution. When op is 'get', the payload JSON may be empty or include limit and sort parameters. The worker must parse payload as authoritative JSON, construct the appropriate HTTP requests, and then return only structured JSON output that strictly validates against the system-provided structured output schema for this tool.