What this category of data looks like
Coal transportation and sales document data mainly comes from transportation and sales contracts, weigh tickets, settlement statements, monthly transportation and sales plans, and delivery notices. Data is updated in business batches, with single document lengths ranging from hundreds of characters for delivery notices to thousands of characters for monthly transportation and sales summaries. Fixed fields include goods name, shipment volume (unit: ton), full name of consignee, transportation route, settlement unit price (unit: yuan/ton), invoicing entity and tax identification number. Some cross-regional transportation and sales documents also include railway/road transportation permit numbers.
What constraints these characteristics impose on the "model access and configuration" link
The fixed proprietary fields and industry-specific units of coal transportation and sales documents require the model to accurately identify and align with business terminology. When accessing the model, ensure the context window covers all complete document fields. The mix of long and short documents requires flexible adjustment of context and output token limits in the configuration. Cross-regional transportation and sales documents include additional non-standard fields such as permit numbers. The model must handle custom field extraction, so enable the configuration item for adapting custom tools. Business data updates in single transportation and sales batches. The model must quickly adapt to document formats of new batches, so the configuration must support quick parameter adjustments to match different document types.
How to set the configurations
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Range | Rationale |
|---|---|---|
maxContext | 8000–12000 token | Covers the context requirements of long documents such as complete coal transportation and sales contracts and monthly summaries, avoiding truncation of key business fields |
maxTokens | 1500–2500 token | Matches the output length required for coal transportation and sales document drafting, covering complete content such as settlement details and transportation instructions |
toolChoice | auto | Supports automatic tool calling to extract proprietary fields from waybills and weigh tickets, adapting to additional information in cross-regional documents |
temperature | 0.3–0.6 | Maintains consistency of document formats and business terminology, avoiding generation of expressions that do not comply with industry specifications |
AIPROXY_API_ENDPOINT | Fill in the locally deployed OneAPI access address | Adapts to the locally deployed FastGPT environment, ensuring normal model invocation links |
AIPROXY_API_TOKEN | Fill in the valid token generated by OneAPI | Completes identity verification for model access, ensuring legal call permissions |
Three common mistakes
- Symptom: After deploying FastGPT locally, OneAPI can ping the model and vector model normally, and the token configuration is correct, but an error is returned when generating coal transportation and sales documents. Cause: The proprietary business fields of coal transportation and sales are not included in the model's context configuration, causing the model to fail to identify proprietary terms and trigger format errors.
- Symptom: The model selection list normally displays all optional models, but only a small number of models are available in the tool call stage. Cause: The model adaptation switch corresponding to
toolChoiceis not enabled, or the tool permissions for the coal transportation and sales scenario are not bound to the corresponding model. - Symptom: Attempting to call the o1-preview model to generate coal transportation and sales documents fails, returning an error that the model is not supported. Cause: The large context compatible model switch in FastGPT's model configuration is not enabled, or
maxContextis not correctly configured to match the context requirements of the large model.
How to confirm the configuration is correct
- Upload a standard coal transportation and sales contract, check whether the drafted document generated by the model accurately identifies proprietary fields such as goods name and shipment volume.
- Select the configured model in the tool call stage, check whether the transportation route and permit number information on the weigh ticket can be extracted normally.
- Adjust the
temperatureparameter, generate two documents of the same type, and verify whether the consistency of business terms meets expectations. - Check the OneAPI invocation logs, confirm that there are no 401 authentication errors or timeout errors, and that the request parameters include the proprietary business fields of coal transportation and sales.
The values provided here are common starting points and should be evaluated against the user's own samples.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-28.