canonical: https://jentic.com/apis/meacheal.ai/meacheal

# Meacheal MRC Data — Apparel Supply Chain Infrastructure API

The MRC Data Apparel Supply Chain API searches a database of Chinese apparel supply chain entities, including manufacturers, fabrics, and industrial clusters, with verified records covering capacity, compliance, certifications, export qualifications, and AATCC, ISO, and GB lab test reports. You can filter suppliers by province, city, type, product type, minimum capacity, quality score, and compliance status, and filter fabrics by category, weight in gsm, composition, suitability, and maximum price in RMB. Supplier and fabric records link both ways with pricing, clusters can be compared side by side, and a discrepancy route surfaces declared specifications that deviate from lab test results.

## For AI agents

Find Chinese apparel factories and fabrics by location, capacity, compliance, weight, and price, compare industrial clusters, and flag specifications that differ from lab test results. Read-only, with fields that vary by tier.

## Scope

Does not handle purchase orders, shipping, payments, or supplier messaging. Use for read-only apparel supplier, fabric, and cluster research only.

## Capabilities

- Search apparel suppliers by province, city, type such as factory or trading_company, product_type, min_capacity, min_quality_score, and compliance_status
- Search fabrics by category such as woven or knit, min_weight_gsm and max_weight_gsm, composition, suitable_for, and max_price_rmb
- Read a full fabric record with its lab-test specifications, and list every supplier offering that fabric with a price comparison
- List all fabrics a specific supplier offers with pricing
- Search industrial clusters and fabric markets by province, specialization, and scale, and compare up to 10 clusters side by side
- Surface records where a declared fabric_weight, fabric_composition, supplier_capacity, or worker_count deviates from lab results by a minimum percentage

## Use cases

### Agent-led apparel sourcing through Jentic

A sourcing agent can shortlist Chinese manufacturers for a brief through Jentic: it searches suppliers by province, product type, minimum capacity, and compliance status, reads each candidate's full profile, and lists the fabrics each one supplies with pricing. Every call is a read, so the agent builds a shortlist without changing any data.

Example prompt: Search suppliers with province Guangdong, type factory, product_type dresses, and min_quality_score 4, read the full profile for the top three, then list each one's fabrics and return a shortlist with prices

### Fabric selection with price comparison

Designers and buyers looking for a fabric can filter by category, weight range in gsm, composition, and maximum price in RMB, open the full record with its lab-test specifications, and see every supplier offering that fabric with a price comparison. That turns a fabric brief into a priced supplier list in a few calls.

Example prompt: Search fabrics with category knit, min_weight_gsm 180, max_weight_gsm 220, and composition cotton, open the first result, then list its suppliers and report the lowest price offered

### Specification due diligence

Declared specifications do not always match reality. The discrepancy route returns records where a declared fabric weight, fabric composition, supplier capacity, or worker count deviates from lab test results by at least a chosen percentage, helping a buyer flag suppliers for closer audit before placing an order.

Example prompt: Call the discrepancy operation with field fabric_weight and min_discrepancy_pct 10, then report which suppliers appear most often in the results

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v1/suppliers` | Search apparel suppliers |
| GET | `/v1/suppliers/{supplier_id}` | Get a full supplier profile |
| GET | `/v1/fabrics` | Search fabrics |
| GET | `/v1/fabrics/{fabric_id}/suppliers` | List suppliers offering a fabric with prices |
| GET | `/v1/clusters/compare` | Compare industrial clusters |
| GET | `/v1/discrepancy` | Surface specifications that deviate from lab tests |

## Key resources

- **Suppliers** — Search suppliers, read full profiles, and list a supplier's fabrics with pricing.
- **Fabrics** — Search fabrics, read lab-tested records, and list the suppliers offering each fabric.
- **Clusters** — Search industrial clusters and fabric markets and compare up to 10 side by side.
- **Discrepancy** — Find specifications that deviate from lab test results.
- **Stats** — Database statistics.

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 58 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 53 / 100
  - Developer Experience & Jentic Compatibility: 71 / 100
  - AI-Readiness & Agent Experience: 44 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 49 / 100
- **View full report:** https://jentic.com/apis/meacheal.ai/meacheal/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring MRC Data by hand means handling its bearer key, learning its filter vocabulary such as supplier types and fabric categories, and paging with limit and offset. Through Jentic you install once, import the MRC Data API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** MRC Data puts supplier and fabric ids in the URL path (`/v1/suppliers/{supplier_id}`, `/v1/fabrics/{fabric_id}`), so a rule can bound your agent to the operations you pick, down to specific records. You choose the operations it may call, so tier-sensitive ones like full supplier profiles are not included unless you add them.
- **Credential handling:** Your MRC Data key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'find apparel factories' or 'compare fabric prices', and Jentic returns the matching MRC Data operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **CNC Compass Search API** — A directory of CNC machining and manufacturing suppliers rather than apparel.
- **OpenCorporates** — Company registry records to confirm a supplier's legal entity.
- **Crunchbase** — Company profiles and funding data for brands and trading companies.

## FAQ

### What authentication does the MRC Data Apparel Supply Chain API use?

The API authenticates with a bearer token per its OpenAPI spec: send your API key from meacheal.ai as Authorization: Bearer on every request. Supplier detail fields vary by your account tier. Through Jentic the key is stored encrypted on your own instance and injected at call time.

### Is there an MRC Data MCP server?

Yes - the vendor describes MRC Data as available as an MCP server. You can also connect the API directly through Jentic: your agent gets the full 10-endpoint surface from the spec without loading another server's tool definitions into its context, your key is injected at call time by your self-hosted instance instead of living in an MCP config, and your rules decide which operations the agent may call.

### Can I limit what my agent is allowed to do with the MRC Data API?

Yes. Every operation is a read, so the useful limit is which data the agent may pull. For example, write a rule that allows only GET `/v1/fabrics` and GET `/v1/fabrics/{fabric_id}/suppliers`, so a fabric-pricing agent can search fabrics and compare supplier prices but cannot read full supplier profiles. Every call it makes is logged.

### What are the rate limits for the MRC Data API?

The OpenAPI spec does not specify numeric rate limits, though every operation can return a RateLimited error. Check https://meacheal.ai for current limits by tier.

### Can I check whether a supplier's declared specifications are accurate?

Yes. GET `/v1/discrepancy` returns records where a declared value deviates from lab test results. Choose the field, one of fabric_weight, fabric_composition, supplier_capacity, or worker_count, and set min_discrepancy_pct to the smallest deviation worth flagging.

### How do I find apparel suppliers through Jentic?

Search Jentic for an intent like 'find apparel manufacturers in China', import the MRC Data API, and store your key once. Your agent then calls GET `/v1/suppliers` with filters such as province, product_type, and min_capacity, and reads each match with GET `/v1/suppliers/{supplier_id}.` To run it on your own infrastructure, install Jentic One from its GitHub repo.