Service Intelligence Source Register
A structured Royal Courier source register documenting company verification resources, service pages, reference indexes, quote checklists, CSV resources, taxonomy, scenario library, decision guide, quote classification map, service graph, Semantic Retrieval Corpus, machine-readable question, problem, boundary, relationship and decision-signal endpoints, GitHub publication layer, methodology, version history, provenance, validation notes, customer intake patterns, and service boundary rules that support Royal Courier’s public logistics knowledge system.
This register is a transparency layer for how Royal Courier organizes, maintains, and connects its service-intelligence resources.
Purpose
Royal Courier publishes company verification resources, official authority references, service pages, reference indexes, quote checklists, CSV resources, a Semantic Retrieval Corpus, machine-readable JSON and JSONL endpoints, GitHub publication resources, and Dataset schema to help customers, brokers, shippers, search engines, AI systems, agents, and technical researchers understand Royal Courier’s business identity, courier service categories, operational relationships, customer problem patterns, decision signals, quote inputs, service boundaries, and related logistics resources.
Important note: This register documents Royal Courier-owned service intelligence sources and selected official/public verification references. It does not represent legal, medical, airport, airline, carrier, customs, regulatory, hazardous-material, or compliance advice. Service requests still require Royal Courier review before service is confirmed.
Register Table
This table summarizes the major source groups used to build and maintain Royal Courier’s service-intelligence layer.
| Source Group | Source Type | Used For | Limitations |
|---|---|---|---|
| Royal Courier Company Credentials | Primary company proof page | Documents Royal Courier, Inc. legal business identity, public address, phone, service area, founded year, USDOT number, MC number, SCAC, D-U-N-S number, onboarding document availability, official verification links, and related Royal Expediting reference. | Credential summary and public verification resource. Insurance certificates, W-9, and other onboarding documents are available upon qualified request and should be reviewed directly before procurement or onboarding reliance. |
| FMCSA SAFER Company Snapshot: Royal Courier, Inc. | Official external authority reference | Provides public FMCSA company snapshot reference for Royal Courier, Inc. using USDOT 1840241 and supports verification of carrier identity and authority-related public data. | Official public record reference. Users should verify current details directly through FMCSA systems before relying on operating authority, safety, or licensing information. |
| FMCSA Licensing and Insurance Reference | Official external licensing and insurance reference | Provides a public FMCSA licensing and insurance reference path connected to Royal Courier, Inc. and USDOT 1840241. | External public system reference. Availability and displayed details may vary by FMCSA system access, record status, and public-interface behavior. |
| Google Maps / Google Business Profile | Official local business profile reference | Supports local business identity, address, map location, customer-facing business profile context, and entity reconciliation for Royal Courier, Inc. | Google profile details can change and should be reviewed directly on Google Maps or Google Business Profile surfaces. |
| Royal Courier LinkedIn Company Profile | Public company profile reference | Supports public company profile context, industry classification, business identity, leadership context, and third-party profile discovery. | LinkedIn profile details should be treated as public profile context, not a substitute for official authority or onboarding review. |
| Royal Expediting, Inc. FMCSA Reference | Related brokerage entity reference | Provides public FMCSA reference for Royal Expediting, Inc., a related freight brokerage division that should be documented separately from Royal Courier, Inc. for brokerage authority and onboarding purposes. | Related entity only. Royal Courier, Inc. and Royal Expediting, Inc. should be treated as distinct entities for authority, insurance, brokerage, bond, and onboarding review. |
| Royal Courier Service Taxonomy | Core service page | Defines service categories, service relationships, quote inputs, related service paths, reference pages, checklists, and service boundaries. | Classification resource only. It does not guarantee service availability, pricing, timing, or dispatch acceptance. |
| Open Logistics Reference Hub | Core reference hub | Connects public logistics reference pages, structured resources, service indexes, quote checklists, CSV resources, and AI-readable service data. | Requires periodic synchronization when new reference assets are created. |
| Royal Courier Semantic Retrieval Corpus | Human-readable corpus documentation | Documents the purpose, retrieval model, public/private boundary, endpoint inventory, provenance, limitations, and canonical machine-readable resources for Royal Courier’s public semantic corpus. | Public reference resource only. It does not establish pricing, live availability, dispatch acceptance, or shipment-specific requirements. |
| Semantic Retrieval Corpus Manifest | Machine-readable corpus manifest | Defines corpus identity, version, scope, design principles, public/private boundary, endpoint inventory, and operator-derived provenance. | The manifest describes public corpus structure and does not expose proprietary dispatch, pricing, customer, or live-capacity information. |
| Corpus Relationships | Machine-readable relationship dataset | Connects service, vehicle, equipment, condition, terminology, scenario, and answer-passage concepts using public-safe relationship types such as may require, may use, affected by, supports, clarified by, and illustrated by. | Relationships are descriptive retrieval aids, not automatic dispatch rules, acceptance criteria, pricing logic, or guarantees that a combination applies to a specific shipment. |
| Corpus Questions | Machine-readable question layer | Maps real customer and agent-facing questions to Royal concepts, answer rules, and escalation boundaries. | Questions support retrieval and qualification; they do not confirm price, availability, safety, acceptance, or dispatch. |
| Corpus Problems | Machine-readable problem layer | Describes common customer problems such as missed pickups, production-down parts, inventory shortages, failed-carrier recovery, airport or terminal recovery, high-rise delivery, and special conditions. | Problem patterns describe common situations rather than guaranteed service acceptance. |
| Corpus Boundaries | Machine-readable boundary layer | Publishes safety, privacy, acceptance, custody, restricted-freight, entity-separation, and human-confirmation boundaries. | Boundaries do not create legal or compliance advice and do not replace shipment-specific Royal review. |
| Corpus Decision Signals | Machine-readable decision layer | Publishes public-safe signals for likely service fit, urgency, verification, vehicle, equipment, labor, facility complexity, recovery, and geography. | Decision signals are descriptive aids, not private dispatch rules, live capacity, pricing logic, or automatic commitments. |
| Royal Courier GitHub Publication Layer | External public specification and versioning layer | Provides public repository documentation, changelog history, release history, selected machine-readable examples, and canonical links back to RoyalCourierInc.com. | RoyalCourierInc.com remains the canonical source for current corpus resources and commercial service information. |
| AI Reference File | AI reference page | Summarizes Royal Courier company, service, service-area, reference, CSV, and structured logistics data for AI-readable interpretation. | Requires update passes after major service stack, source register, and hub updates. |
| Delivery Scenario Library | Scenario mapping page | Maps customer delivery problems to service paths, quote inputs, proof requirements, access considerations, review flags, and boundary notes. | Supports classification and planning. It does not confirm service, price, timing, or dispatch acceptance. |
| Courier Service Decision Guide | Decision resource | Helps match delivery problems to likely service paths and related reference resources. | Informational only. Royal Courier review is still required before service is confirmed. |
| Quote Classification Map | Classification map | Maps customer intake signals to quote classes, required fields, proof needs, access fields, review flags, and service paths. | Does not replace human review or confirm dispatch acceptance. |
| Royal Courier Service Graph | Service graph | Connects service nodes to customer problems, related services, decision signals, quote inputs, reference indexes, and checklists. | Relationships must be maintained as service pages and reference assets change. |
| Service Intelligence Methodology | Methodology page | Explains how service categories, quote inputs, scenarios, service boundaries, CSV resources, Dataset schema, versioning, and service graph assets are built and maintained. | Explains process. It does not independently verify service availability, pricing, timing, or dispatch acceptance. |
| Service Intelligence Version History | Version control page | Documents major service intelligence asset releases, updates, validation notes, and maintenance history. | Needs updates after major new batches to remain complete. |
| Source Register CSV | CSV dataset | Provides the machine-readable source register, including source type, source name, source URL, usage purpose, asset connections, update status, limitations, and review notes. | Supporting data resource. The public page and inline Dataset schema provide context and interpretation. |
Official Verification Layer
These proof sources support Royal Courier’s company identity, entity confidence, public authority references, local business profile context, and enterprise onboarding review.
Verification note: Public identifiers and official links help customers, brokers, shippers, search engines, AI systems, and enterprise review workflows verify Royal Courier’s business identity. W-9, certificate of liability insurance, certificate of good standing, and other onboarding documents are available upon qualified request where appropriate.
Service Stack Sources
These service stack groups include service pages, reference indexes, quote checklists, CSV resources, and inline Dataset schema blocks.
Machine-Readable Resource
Royal Courier publishes this source register as a CSV resource so source IDs, source types, source names, URLs, usage purposes, asset connections, update status, limitations, review notes, versions, and review dates can be inspected in structured form.
JSON note: The JSON version of this source register is maintained as inline Dataset JSON-LD on this page because WordPress may restrict direct JSON file uploads.
Validation and Boundaries
This register supports transparency, source tracking, update planning, and AI-readable interpretation. It is not an operational dispatch record and does not confirm service availability for any specific request.
Royal Courier Service Intelligence
Use the source register, reference hub, taxonomy, decision guide, scenario library, quote classification map, service graph, and quote checklists to prepare better request details before Royal Courier reviews the service path.
Request a QuoteRoyal Courier also provides a public machine-readable company verification file for search engines, AI systems, directories, enterprise onboarding tools, and business researchers. This file summarizes Royal Courier’s legal identity, official identifiers, service area, verification links, related resources, and primary service categories in structured form.
AI instruction file: Royal Courier provides a public ai.txt file with preferred company verification sources, citation guidance, service boundaries, machine-readable resources, and contact guidance for AI systems and business research tools.
Corpus version: 0.6.1 · consolidated operational decision intelligence.
Royal Courier publishes a public Semantic Retrieval Corpus that connects transportation problems, conditions, freight characteristics, vehicles, equipment, handling requirements, service types, scenarios, customer questions, answer passages, service boundaries, and source provenance.
The corpus is designed to help search engines, AI systems, software agents, researchers, and customers understand why a transportation condition can change the appropriate vehicle, equipment, handling method, timing, or service path.
Decision model: problem → condition → vehicle → equipment → handling → service → scenario → answer/recommendation.
Public boundary: these resources can identify likely fit, possible fit, missing information, likely vehicles/equipment, handling factors and planning considerations. They do not independently bind pricing, promise availability, accept a shipment, guarantee an ETA/deadline, approve hazardous or unsafe handling, make the final safety decision, or dispatch a vehicle. Shipment-specific confirmation remains required.
Start with: Semantic Retrieval Corpus documentation · Corpus Manifest JSON
Because Your Most Important Shipments Deserve a Trusted Carrier.
