Vehicle RC Verification AI Agent / LLM
VerificationEverything an AI coding assistant needs to write a working Vehicle RC Verification integration without opening another page: endpoint, authentication, parameters, a real request, both response shapes and the platform rules it cannot infer from a single example. Copy the brief below and paste it into Claude, Cursor, GitHub Copilot, ChatGPT or any other agent.
Machine-readable spec — Markdown
# Vehicle RC Verification API — Way2API®
- **Endpoint:** `POST https://app.way2api.com/api/v1/rc/verify`
- **Auth:** `Authorization: Bearer YOUR_API_KEY` (or `X-API-Key: YOUR_API_KEY`)
- **Content-Type:** `application/json`
- **Category:** Verification
- **Availability:** Available in India
- **Docs:** https://app.way2api.com/documentation/vehicle-rc
## What it does
Vehicle RC Verification API — Fetch full Registration Certificate (RC) details for any Indian vehicle using its registration number. Returns comprehensive vehicle information including owner name, vehicle make/model, fuel type, insurance details, fitness status, tax details, PUCC status, financer info, and more. Useful for used-car platforms, insurance underwriting, fleet management, RTO compliance, and loan verification. Optional chassis and engine number parameters for additional cross-verification.
## Request body (application/json)
| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `rc_number` | string | yes | Vehicle registration number (e.g. DL3CAB1234, MH12AB1234). |
| `chassis_number` | string | no | Chassis number for additional verification (optional). |
| `engine_number` | string | no | Engine number for additional verification (optional). |
## Example request
```bash
curl -X POST https://app.way2api.com/api/v1/rc/verify \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"rc_number":"DL3CAB1234"}'
```
## Success response — 200
```json
{
"status": "SUCCESS",
"status_code": 200,
"charged": true,
"success": true,
"message": "",
"message_code": "OK",
"order_id": "W2A1739512345abcdef01",
"data": {
"order_id": "W2A1739512345abcdef01",
"result": {
"rc_number": "DL3CAB1234",
"fit_up_to": "2037-03-20",
"registration_date": "2022-03-21",
"owner_name": "Anjali Deshmukh",
"father_name": "",
"present_address": "12 Sector 9, Dwarka, New Delhi, 110075",
"permanent_address": "12 Sector 9, Dwarka, New Delhi, 110075",
"vehicle_category": "LMV",
"vehicle_chasi_number": "MA1AB2CD3EF456789",
"vehicle_engine_number": "0000A123",
"maker_description": "BMW INDIA PVT LTD",
"maker_model": "BMW 220I GRAN COUPE M SPORT",
"body_type": "SEDAN",
"fuel_type": "PETROL",
"color": "SNAPPER ROCKS BLUE M",
"norms_type": "BHARAT STAGE VI",
"financer": "EXAMPLE BANK LTD",
"financed": true,
"insurance_company": "Example General Insurance Co. Ltd.",
"insurance_policy_number": "P1234567890",
"insurance_upto": "2026-05-20",
"manufacturing_date_formatted": "2022-03",
"registered_at": "SOUTH DELHI, Delhi",
"rc_status": "ACTIVE"
}
}
}
```
## Error response — 422
```json
{
"status": "SUCCESS",
"status_code": 422,
"charged": true,
"success": false,
"message": "Verification Failed.",
"message_code": "VERIFICATION_FAILED",
"order_id": "W2A1739512345abcdef01",
"data": {
"order_id": "W2A1739512345abcdef01",
"error_code": "verification_failed",
"result": {
"rc_number": "KA12AC3456",
"registration_date": null,
"owner_name": null,
"vehicle_category": null,
"maker_model": null,
"fuel_type": null,
"rc_status": null
}
}
}
```
## Integration rules
- Every response is JSON carrying `status`, `status_code`, `charged`, `success`, `message`, `message_code` and (once a call reaches the provider) `order_id`. The verification payload is under `data.result`.
- `charged` (boolean) is the authority on billing. Do NOT infer it from the HTTP status: `422` is returned both for input we rejected (not charged) and for a lookup the provider ran and billed us for that returned a negative result (charged).
- `message_code` is a fixed vocabulary — branch on it instead of parsing `message`. Values: `OK`, `ACCEPTED`, `PROVIDER_NO_RESPONSE`, `VERIFICATION_FAILED`, `NO_RECORD_FOUND`, `INVALID_INPUT`, `REQUEST_FAILED`, `MISSING_API_KEY`, `INVALID_API_KEY`, `INSUFFICIENT_BALANCE`, `NO_API_ACCESS`, `NOT_FOUND`, `RATE_LIMITED`, `INTERNAL_ERROR`, `PROVIDER_UNAVAILABLE`.
- `success` reports the verification outcome; `status` reports the ORDER lifecycle (`SUCCESS`/`PENDING`/`FAILED`). They differ on a charged negative result: the order completed and was billed while the verification did not pass.
- A failed verification is still a successful HTTP call — the outcome lives in the response body, so do not treat `200` as "verified".
- Status codes: `200` result returned, `202` pending or provider did not respond (both charged — quote the `order_id`), `401` missing/invalid key, `402` insufficient balance, `403` no access to this service, `422` see `charged`, `429` rate limited (honour the `Retry-After` header), `503` temporarily unavailable.
- Rate limits are per API key, per service, on a 1-minute sliding window.
- Load the API key from an environment variable or secret store. Never hard-code it, never commit it, and never ship it in client-side code — calls must be made from your backend.
Prompts to pair it with
- Write a production-ready Vehicle RC Verification integration in PHP using this spec, with error handling and retries.
- Given this spec, generate typed request/response models and a client class.
- Review my existing Vehicle RC Verification integration against this spec and list what I handle incorrectly.
⚠ Before you paste generated code
Never let an assistant hard-code your API key — load it from an environment variable or a
secret store, and call this endpoint from your backend only. A failed verification is still a
successful HTTP call, so check the success field in the body
rather than treating 200 as verified.