crewpass.co.uk valid
CrewPass Partner API
Scope-gated, consent-intersected, multi-tenant read API onto CrewPass crew, vessel, document, and compliance data. v1 is read-only plus webhooks, for management companies. Auth = partner API key (`cpk_live_*` / `cpk_test_*`) as a Bearer token over TLS; reads are not signed. Access requires `granted ∩ consented` scopes and the crew being on your fleet (derived from your CrewPass employer account). Base URLs: `https://partners.crewpass.co.uk` (production), `https://devpartners.crewpass.co.uk` (dev
- Authority
- 45 reach 0 · trust 5 · quality 25 · freshness 15
- Tier
- listed
- llms.txt
- https://docs.crewpass.co.uk/llms.txt
- llms-full.txt
- https://docs.crewpass.co.uk/llms-full.txt
- Sections
- 7
- Links
- 27
- Size
- 4260 bytes
- Country
- United Kingdom Country-code domain
- Country evidence
- No published address evidence collected yet
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-26T09:55:44.818Z
- Last checked
- 2026-10-26T09:55:58.272Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-26T09:55:44.827Z. Cached copy · Source on crewpass.co.uk
# CrewPass Partner API
> Scope-gated, consent-intersected, multi-tenant read API onto CrewPass crew, vessel, document, and compliance data. v1 is read-only plus webhooks, for management companies. Auth = partner API key (`cpk_live_*` / `cpk_test_*`) as a Bearer token over TLS; reads are not signed. Access requires `granted ∩ consented` scopes and the crew being on your fleet (derived from your CrewPass employer account). Base URLs: `https://partners.crewpass.co.uk` (production), `https://devpartners.crewpass.co.uk` (dev/sandbox). All endpoints under `/api/v2/`.
## Get started
- [Introduction](https://docs.crewpass.co.uk/introduction.md): What the API is, what you can do, the access/consent model, base URLs.
- [Quickstart](https://docs.crewpass.co.uk/quickstart.md): End-to-end management flow — vessels → fleet → crew lookup → profile/documents/compliance/download, with cURL, Python, and Node samples.
- [Authentication](https://docs.crewpass.co.uk/authentication.md): the API key as a Bearer token over TLS for reads.
## Guides (what you can do)
- [List your vessels](https://docs.crewpass.co.uk/guides/vessels.md): GET /employers/me/vessels — the vessels on your account.
- [See your crew](https://docs.crewpass.co.uk/guides/crew.md): The fleet roster (verification + background-check status + expiring counts), paging, and crew lookup by email.
- [Read a crew profile](https://docs.crewpass.co.uk/guides/profiles.md): Base profile + consent-gated identity block + photo proxy.
- [Documents & downloads](https://docs.crewpass.co.uk/guides/documents.md): List documents (issuer, verification status, classification), mapping classifications to your own types, the two-step branded download flow, and a "download all" example.
- [Check compliance](https://docs.crewpass.co.uk/guides/compliance.md): What feeds compliance, overall_status, and the unified requirement matrix (medical / STCW / certificate / qualification) with the document that satisfies each.
- [Background-check status](https://docs.crewpass.co.uk/guides/background-checks.md): The standardised, provider-agnostic status vocabulary.
## Webhooks
- [Webhooks](https://docs.crewpass.co.uk/webhooks.md): How changes reach you — envelope, the outbound signing scheme (`v1=hmac(secret,"{ts}.{body}")`, which differs from request signing), event catalogue, payloads, retry/dead-letter, and a receiver-verification example.
## Reference
- [Document codes](https://docs.crewpass.co.uk/reference/document-codes.md): The versioned list of document classes, category codes, STCW codes and evidence sources used by the `classification` block.
- [Rate limits](https://docs.crewpass.co.uk/rate-limits.md): Per-partner token-bucket budgets and 429 handling.
- [Errors overview](https://docs.crewpass.co.uk/errors.md): The error envelope and the full code catalogue.
- [invalid_api_key (401)](https://docs.crewpass.co.uk/errors/invalid_api_key.md)
- [invalid_signature (401)](https://docs.crewpass.co.uk/errors/invalid_signature.m
…Machine-readable: GET /v1/resolve?q=crewpass.co.uk · GET /v1/domain/crewpass.co.uk · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage crewpass.co.uk, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for crewpass.co.uk:
1. POST https://agentwebmap.com/v1/sites/crewpass.co.uk/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://crewpass.co.uk/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/crewpass.co.uk/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/crewpass.co.uk).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.