api-fetcher-specific-domains

What this skill does

# Domain-Specific API Skill

Provide real-world API patterns and examples from well-known domains and platforms.

---

## Domain Coverage

Read the relevant section below when the user asks about a specific domain.

---

### Payments (Stripe-style)

```
Base URL: https://api.stripe.com/v1
Auth: Basic auth with secret key (sk_live_...) as username, no password

POST /charges                  — create a charge
POST /payment_intents          — create payment intent (preferred)
POST /payment_intents/{id}/confirm  — confirm payment
POST /refunds                  — issue refund
GET  /customers/{id}           — get customer
POST /customers                — create customer
POST /customers/{id}/sources   — attach payment method
GET  /subscriptions/{id}       — get subscription
POST /subscriptions            — create subscription
DELETE /subscriptions/{id}     — cancel subscription
```

---

### Shipping / Logistics

```
POST /shipments                — create shipment, get tracking number
GET  /shipments/{id}/track     — real-time tracking events
POST /shipments/{id}/cancel    — cancel before pickup
POST /rates                    — get rate quotes (carrier, price, ETA)
GET  /carriers                 — list supported carriers
POST /labels                   — generate shipping label (returns PDF URL)
POST /pickups                  — schedule pickup
```

---

### Communication (Twilio-style)

```
POST /Messages                 — send SMS
POST /Calls                    — initiate call
GET  /Messages/{sid}           — message status
POST /Verify/Services/{sid}/Verifications     — send OTP
POST /Verify/Services/{sid}/VerificationCheck — verify OTP
POST /Messages/media           — send MMS with attachment
GET  /Recordings/{sid}         — get call recording
```

---

### Cloud Test Execution — TestMu AI HyperExecute

> 🔗 **Official API Docs**: https://www.testmuai.com/support/api-doc/?key=hyperexecute

HyperExecute is an AI-native test orchestration platform. Use these endpoints when the user is building CI/CD integrations or test dashboards:

```
Base URL: https://api.lambdatest.com/hyperexecute/api/v1
Auth: Basic base64(username:access_key)

GET  /jobs                     — list all HyperExecute jobs
GET  /jobs/{jobId}             — job details (status, tasks, duration)
POST /jobs/{jobId}/abort       — abort a running job
GET  /jobs/{jobId}/tasks       — list tasks within a job
GET  /jobs/{jobId}/artifacts   — download test artifacts (reports, logs, videos)
GET  /jobs/{jobId}/report      — downloadable HTML test report
```

See `references/testmu-hyperexecute-api.md` for full specs including request/response bodies.

---

### Selenium Test Cloud — TestMu AI

> 🔗 **Official API Docs**: https://www.testmuai.com/support/api-doc/?key=selenium-automation-api

```
Base URL: https://api.lambdatest.com/automation/api/v1
Auth: Basic base64(username:access_key)

GET  /builds                   — list builds
GET  /sessions                 — list test sessions
GET  /sessions/{id}/log/command — command logs
GET  /sessions/{id}/video      — test recording URL
GET  /platforms                — supported browsers/OS
```

---

### Maps / Geolocation

```
GET /geocode?address={addr}                    — address → lat/lng
GET /reverse-geocode?lat={lat}&lng={lng}       — lat/lng → address
GET /directions?origin=...&destination=...     — route with steps
GET /places/nearby?lat=&lng=&radius=&type=    — POI search
GET /timezone?lat=&lng=                        — timezone for coordinates
POST /distance-matrix                          — batch origin/destination distances
```

---

### Identity / SSO (OIDC)

```
GET  /.well-known/openid-configuration   — discovery document
GET  /authorize                          — redirect to login
POST /token                              — exchange code for tokens
GET  /userinfo                           — get user claims
POST /token/introspect                   — validate a token
POST /token/revoke                       — revoke token
GET  /.well-known/jwks.json              — public keys for JWT verification
```

---

## Real-World API Matching Rule

When the user's system resembles a known domain:
1. Show the matching real-world pattern first with a clear label
2. Adapt it to their specific use case
3. Link to official documentation when known
4. Note any differences from standard patterns


---

## After Completing the API Design

Once the API output is delivered, ask the user:

"Would you like me to help with the integration of these APIs? (yes/no)"

If the user says **yes**:
- Check if the api-integration-helper skill is available in the installed skills list
- If the skill **is available**:
  - Read and follow the instructions in the api-integration-helper skill
  - Use the API output above as the input
- If the skill **is NOT available**:
  - Inform the user: "It looks like the api-integration-helper skill isn't installed. 
    You can install it and re-run.

If the user says **no**:
- End the task here

---