# Common Integration Patterns

## Known Component ID → Direct Detail

1. Select the video or image Component ID route.
2. Send the identifier as the path parameter.
3. Use the returned UUID for media or later detail workflows when needed.

This is the recommended approach for a known Component ID.

## Discover → Retrieve → Review

1. Use structured or Natural Language Search.
2. Select a result and retain its UUID.
3. Retrieve the detail record.
4. Request a player or viewer URL only when required.

## Search → Domain GenAI

1. Use search to verify the topic and filters.
2. Ask Domain GenAI for a supported synthesis.
3. Present the answer together with its returned sources.
4. Keep the `conversation_id` only while follow-up turns are expected.
5. Delete the conversation when the integration no longer needs it.

## Geo Manifest Traversal

1. Start a Geo Manifest request without a cursor.
2. Render returned items or GeoJSON features.
3. If `next_cursor` is present, repeat the exact original request parameters with that cursor.
4. If a cursor is rejected, restart the same request without a cursor.
5. Stop when `complete` is true or `next_cursor` is null.

## MCP Client

1. Connect `/mcp-icd` or `/mcp-all`.
2. Store the key as a Bearer-token secret.
3. Let the client discover tool schemas and behavior annotations.
4. Route a known Component ID to its direct tool.
5. Avoid automatic retries for Domain GenAI calls.

## Monitoring

- Poll only as often as the use case requires.
- Use date filters or continuation controls to avoid repeatedly retrieving old results.
- Honor rate-limit responses and apply jittered backoff.
- Do not use search-result totals to infer records outside the key's authorized scope.