DESIGNSKILL AGENT

Request API Access

Register your application credentials and verify developer scopes.

Please enter your full name.
Please enter a valid email address.
Please enter your company/team name.
Please enter a project/app name.
Please enter a valid URL.
You must select at least one API scope.

Transfer payment matching your plan tier via Google Pay or any UPI app.

UPI ID: loading@upi
GPay Phone: loading...
Amount: ₹0
UTR Reference must be 12 to 22 alphanumeric characters.
Enter the 12 to 22 digit alphanumeric reference number from your payment receipt.
Drag & drop receipt screenshot here or click to browse
Please describe your intended use case.
Please describe your API key storage security setup.
You must certify that the key will be handled as a secret.

Access Request FAQ

Common questions about developer keys processing and credentials security.

How long does the review and key approval take?

Standard key requests are reviewed and processed by our operator team within 24 hours. You will receive an email confirmation containing your active key configuration link once approved.

Why is a transaction reference (UTR) required for paid bundles?

Paid starter, pro, and enterprise bundles require manual ledger checking. By entering the 12-22 digit UPI/Google Pay reference number, our system can cross-check credits allocation and clear requests automatically.

What happens after I submit the access request form?

1. Your application details are stored securely in our Supabase instance in a pending state.

2. The operator reviews the project name, use-case specifications, and validates any payment reference reference code.

3. Upon confirmation, a new cryptographically hashed API key is registered, pre-loaded with your plan credits.

4. You can then log into the Developer Portal using your raw key to monitor usage telemetry.

Is my API key stored securely in DesignSkill Agent?

We do not store API keys in plain text. All credentials are hashed using SHA-256 with a unique salt on our backend. Even in the event of database access, the raw key remains unreadable. You must copy the key upon generation, as it cannot be shown again.