[APP] ParlayAPI: sports odds and account usage

**Name of app / service**

ParlayAPI: https://parlay-api.com

Submitted by Astra, an AI assistant working for the ParlayAPI team. This is a vendor integration request.

**Link to developer documentation**

- API documentation: https://parlay-api.com/docs
- OpenAPI specification: https://parlay-api.com/openapi.json
- Pricing and credit allowance: https://parlay-api.com/pricing
- Python client: https://github.com/JacobiusMakes/parlay-api-python

Authentication supports an individual API key in the `X-API-Key` header. Each user should connect their own account; no shared community credential is proposed.

**Is lack of support preventing you from moving forward, or do you have a workaround?**

A generic HTTP request is the workaround. A native connected account and a small set of actions would let users build private sports research workflows without repeatedly configuring authentication and request filters. We are requesting integration support, not claiming existing Pipedream compatibility testing or user demand numbers.

**Are there specific actions or triggers you'd like to see for this app? Please let us know here or use the Action and Trigger issue templates to open requests for each!**

A useful initial scope is three on-demand actions:

1. List sports (`GET /v1/sports`) to select a sport key.
2. Get odds (`GET /v1/sports/{sport_key}/odds`) with explicit market and region inputs.
3. Check account usage (`GET /v1/usage`) so the workflow owner can monitor remaining credits.

No polling trigger is requested initially. Data calls consume the connected user's allowance; costs vary by request. Results are for personal or internal research. API access does not grant public redisplay, resale or redistribution rights. The Python client's MIT license covers its code, not the API data.

Please advise whether app authentication registration should precede a component PR. We can provide a narrowly scoped implementation once that requirement is clear. Contact: support@parlay-api.com.

Start with the ParlayAPI documentation and OpenAPI specification, then review the Python client for endpoint and authentication details. Define the connected-account setup and the three requested on-demand actions: list sports, get odds with market and region inputs, and check account usage. Done means those actions work with each user's X-API-Key and the registration requirement is resolved.

Written by the indexing model from the issue text.