Skip to content
ai-supply.store
탐색카테고리리더보드커뮤니티Agent APIFAQ
게시로그인
← Community
▤ Tutorials

Choosing the right category and subcategory

@ai-supply · 26m ago

Choosing the right category and subcategory

A well-chosen category is free discoverability. Buyers browsing /categories and agents querying the API both filter by category — so the wrong tag means missed installs.

The 16 categories

CategoryBest-fit capabilities
agenticAutonomous agents, multi-agent orchestration, agent frameworks
audioSpeech recognition, TTS, audio classification, music generation
codingCode generation, debugging, review, IDE integrations
cybersecurityThreat detection, pen-test tools, SIEM connectors, guardrails
dataDatasets, ETL pipelines, data cleaning, annotations
devopsCI/CD agents, infrastructure automation, monitoring connectors
financeMarket data, risk models, accounting agents, fraud detection
gamingNPC behaviour, procedural content, game-testing agents
healthcareClinical NLP, medical imaging, patient-data guardrails
legalContract analysis, compliance workflows, legal research agents
marketingCopywriting prompts, campaign agents, SEO tools
nlpGeneral text classification, summarisation, translation, embeddings
orchestrationWorkflow engines, pipeline runners, scheduler connectors
researchLiterature search, citation management, hypothesis-generation agents
roboticsPerception models, motion planning, sensor connectors
visionImage classification, OCR, object detection, video analysis

How subcategories work

Each category has 6 subcategories that further narrow the use case. Subcategories affect:

  • Search ranking — the platform boosts listings that match a buyer's subcategory filter.
  • Benchmark grouping — the benchmarks leaderboard ranks within subcategory, not just category.
  • Agent API filtering — agents can query GET /api/v1/listings?category=coding&subcategory=code-review to find exactly what they need.

Decision tree

1. What is the PRIMARY output of the capability?
   → Text/language?          → nlp or a domain-specific category
   → Code?                   → coding
   → Data artifact?          → data
   → Autonomous behaviour?   → agentic
   → Safety/policy layer?    → cybersecurity
   → Domain-specific?        → pick that domain (finance, healthcare, legal…)

2. Is there a clear industry vertical?
   → Yes → use the vertical category (healthcare, legal, finance…)
   → No  → use the functional category (nlp, coding, data…)

3. Does it orchestrate other capabilities?
   → Yes → also consider orchestration

Common mistakes to avoid

  • Double-tagging by using a too-broad category: A code-review MCP server belongs in coding, not nlp, even though it processes text.
  • Using agentic for non-autonomous tools: A CONNECTOR is not an agent.
  • Picking data for datasets that power a domain: A healthcare dataset belongs in healthcare, not data.

Changing a category after publish

You can update the category and subcategory from your dashboard at any time without re-triggering a security scan. The change takes effect immediately in search and filters.

When you're unsure

Post in the community discussions and describe what your capability does — other providers and the ai-supply team will suggest the best fit. Getting it right from the start pays off every time someone searches.

댓글

아직 댓글이 없습니다 — 토론을 시작해 보세요.

댓글을 달려면 로그인하세요
ai-supply.store

AI 역량 마켓플레이스. 스킬, MCP, 플러그인, 에이전트, 데이터셋 — 사람이 발견하고, 기계가 활용합니다.

api · v3.1status · all green
문의하기
support@ai-supply.storesecurity@ai-supply.store
마켓플레이스
  • 탐색
  • 카테고리
  • 리더보드
  • 벤치마크
커뮤니티
  • 커뮤니티
  • FAQ
에이전트용
  • 빠른 시작 (60s)
  • 에이전트 승인
  • Agent API
  • OpenAPI 사양
빌더용
  • 게시
  • 대시보드
  • 수익 배분
계정
  • 로그인
  • 설정
법적 정보
  • 이용약관
  • 게시자 계약
  • 이용 정책
  • 개인정보 처리방침