You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: rebrand QURL → qURL across user-facing surfaces (#58)
## Summary
Updates the brand spelling to **qURL** (case-sensitive) across
user-visible strings, documentation, and JSDoc comments.
## Why
The product brand is `qURL`. README, the npm-published `package.json`
`description`, JSDoc surfaces (which IDEs and TypeDoc render verbatim),
and the test reporter output were inconsistently spelled `QURL`. This
brings them in line.
## What changed
- `README.md`, `CLAUDE.md`, `package.json` description
- JSDoc `/** … */` comments in `src/{client,errors,types}.ts`
- Test description strings (`it("creates a qURL", …)`) for consistent
reporter output
- CI workflow Slack notify header
## What was intentionally not changed
Identifier-style references kept as-is to preserve the public API:
- Class names: `QURL`, `QURLClient`, `QURLError`, `QURLErrorData`, plus
all error subclasses (`AuthenticationError`, `AuthorizationError`,
`NotFoundError`, `ValidationError`, `RateLimitError`, `ServerError`,
`NetworkError`, `TimeoutError`)
- Field names: `qurl_id`, `qurl_link`, `qurl_site`, `qurl_count`,
`qurls`, plus quota fields
- npm package name (`@layerv/qurl`)
- Import statements and CJS/ESM smoke tests (which assert on `typeof
QURLClient === "function"`)
- `contract/openapi.snapshot.yaml` — synced from upstream OpenAPI spec;
will pick up the rebrand when upstream lands
A few test mock fixtures keep `"detail": "QURL not found"` because they
mirror upstream API responses; these will be updated alongside the
upstream qurl-service rebrand to keep mocks accurate.
## Test plan
- [x] `npm run build` passes (ESM + CJS)
- [x] `npm run format:check` clean
- [x] `npm test` — 67/67 vitest tests pass
- [x] Grep verification: no `QURL` / `Qurl` left in prose contexts
---------
Co-authored-by: Claude Opus 4.7 (1M context) <[email protected]>
TypeScript SDK for the [QURL API](https://docs.layerv.ai) — secure, time-limited access links for AI agents.
7
+
TypeScript SDK for the [qURL™ API](https://docs.layerv.ai) — secure, time-limited access links for AI agents.
8
8
9
-
## Why QURL?
9
+
> **Quantum URL (qURL)** · The internet has a hidden layer. This is how you enter.
10
10
11
-
AI agents need to access protected resources — APIs, databases, internal tools — but giving them permanent credentials is a security risk. QURL creates time-limited, auditable access links that expire automatically. The SDK handles authentication, retries, pagination, and error handling so you can focus on your agent logic.
11
+
## Why qURL?
12
+
13
+
AI agents need to access protected resources — APIs, databases, internal tools — but giving them permanent credentials is a security risk. qURL creates time-limited, auditable access links that expire automatically. The SDK handles authentication, retries, pagination, and error handling so you can focus on your agent logic.
12
14
13
15
## Installation
14
16
@@ -57,12 +59,12 @@ console.log(`Access granted to ${access.target_url} for ${access.access_grant?.e
57
59
| Method | Description |
58
60
|--------|-------------|
59
61
|`create(input)`| Create a protected link |
60
-
|`get(id)`| Get QURL details |
61
-
|`list(input?)`| List QURLs (single page) |
62
-
|`listAll(input?)`| Iterate all QURLs (auto-paginating) |
63
-
|`delete(id)`| Revoke a QURL|
62
+
|`get(id)`| Get qURL details |
63
+
|`list(input?)`| List qURLs (single page) |
64
+
|`listAll(input?)`| Iterate all qURLs (auto-paginating) |
65
+
|`delete(id)`| Revoke a qURL|
64
66
|`extend(id, input)`| Extend expiration |
65
-
|`update(id, input)`| Update QURL properties |
67
+
|`update(id, input)`| Update qURL properties |
66
68
|`mintLink(id, input?)`| Mint a new access link |
67
69
|`resolve(input)`| Resolve token + open firewall |
0 commit comments