Obtaining credentials
this guide explains how to obtain all the credentials and access needed for agent development step 1 get jfrog api token go to https //kyndryl jfrog io https //kyndryl jfrog io/ log in with your kyndryl sso click your user profile (top right corner) → edit profile under authentication settings, click generate an identity token copy and save the generated token securely step 2 repository access no separate taas or additional repository access request is required to pull the bridge agent sdk if your kyndryl sso account can sign in to jfrog, proceed directly with token generation and netrc setup step 3 configure netrc create or edit / netrc cat >> / netrc << 'eof' machine kyndryl jfrog io login your email\@kyndryl com password your jfrog api token eof chmod 600 / netrc option a openai api key (local dev) for local dev mode, you need direct access to openai option a personal openai account go to https //platform openai com/api keys https //platform openai com/api keys sign in or create an account click create new secret ke " copy and save the key (starts with sk ) option b azure openai (kyndryl) contact your team lead for kyndryl azure openai credentials configure environment openai api key=sk your key here openai api base=https //api openai com/v1 bridge platform credentials for bridge dev and production modes, you need bridge platform access get bridge console access request access to bridge console via your team lead or the kaif onboarding team log in to the bridge console at your account specific url create a service id and get the service api key the service api key is not a personal api key — it is the key associated with a service id (a machine/service account) on the bridge platform your agent uses this key to authenticate with the service and get a bearer token how to create a service id log in to the bridge admin console for your account navigate to manage & administer → access management → service ids ) click create service id fill in the details name a descriptive name (e g , incident enrichment agent dev) description purpose of this service id the platform generates a service api key; copy it immediately store it securely; this becomes your service api key env var the key is shown only once at creation time if you lose it, you must create a new service id get account id in bridge console, go to account → settings (or check the url — the account id is in the host name) copy your account id (e g , 697afe33bc0bab35cc54f8ae) the account id also appears in the account specific host url for example https //kaiftestaccount us 697afe33bc0bab35cc54f8ae bridge kyndryl com get kaif host url the kaif host is the global bridge platform url used for , llm, audit, and other platform services this is different from the account specific url \<font color="#f3f4f6"> variable \</font> \<font color="#f3f4f6"> url pattern \</font> \<font color="#f3f4f6"> example \</font> kaif host (global) {{global instance}}https // {{region}} {{global id}}}} bridge kyndryl com https //globalkaiffvt us 6997f3f1ffcf5c8001488dfc bridge kyndryl com bridge mcp server ur (optional) https //{{account name}} {{region}} {{account id}} bridge kyndryl com/kaif/v2/mcp/tools https //kaiftestaccount us 697afe33bc0bab35cc54f8ae bridge kyndryl com/kaif/v2/mcp/tools in bridge dev mode the sdk automatically builds the mcp endpoint from kaif host ({{kaif host}}/kaif/v2/mcp/tools) you only need bridge mcp server url if your mcp server lives on a different host than kaif host ask your kaif platform admin for the correct kaif host url for your environment mcp server access for mcp tools (servicenow, bridge data, etc ), the sdk auto resolves the mcp endpoint from kaif host in bridge dev mode you only need bridge mcp server url if your mcp server runs on a different host the mcp server url is account specific https //{{account name}} {{region}} {{account id}} bridge kyndryl com/kaif/v2/mcp/tools configure env only needed if your mcp server url differs from kaif host bridge mcp server url https //myaccount us abc123def456 bridge kyndryl com/kaif/v2/mcp/tools mcp tool permissions to use specific mcp tools, your account must have them provisioned run the mcp discovery script https //github com/kyndryl agentic ai/bdg sw agents development guide/blob/main/docs/02 new agent development/05 mcp tools discovery md to see what's available for your account common tools \<font color="#f3f4f6"> tool \</font> \<font color="#f3f4f6"> description \</font> \<font color="#f3f4f6"> notes \</font> servicenow search incidents search servicenow incidents primary way to look up incidents servicenow get all incidents list servicenow incidents paginated, up to 100 servicenow create incident create a new incident all 4 fields required bridge execute query query bridge data lake (trino sql) most commonly used bridge list tables list available tables enabled by default bridge list domains list data domains enabled by default tools like servicenow get ticket and servicenow update ticket do not exist on the current mcp server always verify with the discovery script before writing agent code langfuse tracing (optional) for observability and tracing get langfuse credentials request langfuse access from your team lead get your project credentials from langfuse dashboard configure env langfuse secret key=sk lf langfuse public key=pk lf langfuse base url=https //cloud langfuse com