[REQUEST] Arcmira: YouTube Transcript Search integration

Aberta
  • Algo errado?
#8,607 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
35/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
typescript
Domínio
backend-api-design

Direção de pesquisa

Read the contribution guide for staging and inspect the tool, block, icon, and generated catalog registration requirements first. Use the linked OpenAPI contract and search, authentication, and usage documentation to define the two actions, credential handling, outputs, and error behavior. Done means maintainers agree on the native two-action scope and the required registrations are updated.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

Is your feature request related to a problem? Please describe.

This is a first-party proposal from Arcmira. Sim users can connect Arcmira through the generic MCP or API blocks, but there is no native Arcmira block in the current staging registry. A native block could make timestamped YouTube transcript research available through named actions and documented outputs, without hand-authoring HTTP requests or MCP programs.

Describe the solution you'd like

Add an Arcmira integration, displayed as Arcmira: YouTube Transcript Search where the catalog permits descriptive titles, with two initial actions:

  • Resolve a person, channel or company name through GET /v1/entities/resolve. Return the resolution options instead of silently choosing an ambiguous name.
  • Search spoken transcript passages through GET /v1/search, with a user-controlled result limit and optional documented filters. Preserve timestamped source links, speaker information when available, coverage, partial results and access restrictions.

Use the user's account API key as a user-only configuration input, never a model-supplied argument. Pass credentials in the bearer header. Errors should preserve the API status/code and documentation link, including quota, access and rate-limit failures. The initial block covers entity resolution and indexed search. If expanded to Premium transcript retrieval, paid reads use credits from your plan, then your on-demand budget.

API docs: https://arcmira.com/docs

OpenAPI contract: https://api.arcmira.com/v1/openapi.json

Search guide: https://arcmira.com/docs/search

Authentication and usage: https://arcmira.com/docs/authentication and https://arcmira.com/docs/usage-and-billing

Describe alternatives you've considered

  • Existing remote MCP connection: https://mcp.arcmira.com/mcp. It provides broader research and account operations, with its own tool-effect and entitlement rules: https://arcmira.com/docs/mcp-server
  • Generic API block against https://api.arcmira.com/v1 with the user's bearer key.
  • Separate keyless API-documentation MCP at https://arcmira.com/docs/mcp for developers building integrations. This searches documentation, not video transcripts.

Additional context

Would maintainers prefer a native two-action block or a maintained MCP workflow example? The contribution guide targets staging and requires the tool, block, icon and generated catalog registrations. This proposal seeks agreement on the contribution scope. The local search-and-entity-resolution candidate passed the full repository test suite, repository audits and all-workspace typechecking on October 16, 2026. Both actions also succeeded through the native HTTP routes using an isolated read-only test account, with unchanged account usage. These are dated local results; the candidate still needs a refresh against current staging before contribution. The candidate has not been submitted as a PR or accepted by Sim. Free account API access is available within account allowances, with plan-dependent features and freshness. No credentials or private data are included.

Linguagem predominante
TypeScript
Estrelas
29.8k
Forks
3.9k
Merge médio
1h 44min
PRs com merge (30d)
841

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de simstudioai/sim

Todas as issues de simstudioai/sim

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.